DblPlusUngood

9 ms·

31.
by DblPlusUngood 10y ago
Never before have I been so eager to shoot potatoes into the sun.
32.
by DblPlusUngood 10y ago
Obviously a direct translation from English to Russian -- I doubt a Russian would ever actually say this. They should change it to: молодец.
33.
by DblPlusUngood 10y ago
"Thousands of cycles" is definitely not true on modern CPUs. SYSENTER/SYSEXIT takes 150 cycles on my Xeon X3460.
34.
by DblPlusUngood 10y ago
The space overhead is significantly worse for native threading in the presence of many threads since each thread needs both a user and kernel stack. For M:N, there are N kernel stacks.
35.
by DblPlusUngood 10y ago
SIG_IGN is not the same as the signal mask. The result is the same though; I forgot that signal mask is not reset on exec. Damn POSIX signals!
36.
by DblPlusUngood 10y ago
Why is setting the signal handler for SIGHUP to getpid preferable to masking the signal?
37.
by DblPlusUngood 10y ago
Linus' reply: "I detest these patches." https://lkml.org/lkml/2016/8/2/1589
38.
by DblPlusUngood 10y ago
Why do you say "non-standard"? O_NOFOLLOW is specified by POSIX.
39.
by DblPlusUngood 10y ago
It would be great if you could provide specific reasons why FireEngine is able to avoid the overheads which other projects avoid via kernel bypass.
40.
by DblPlusUngood 10y ago
> The advantage of this construct is that you can use the flags set by the increment to test for loop termination, rather than needing an additional comparison. I don't understand your optimization. ZF is also set for dec , so why
41.
by DblPlusUngood 10y ago
My point is simply this: maybe the author wanted to write an OS that he could use on his PC without rewriting all of his programs. Maybe he did not want to do OS interface research.
42.
by DblPlusUngood 10y ago
My point was to compare TOC to "typical generational collectors" (i.e. those using card-marking, which is common). My point was not that TOC is fundamentally different from generational collection.
43.
by DblPlusUngood 10y ago
Tenuring the young object in the write-barrier is not correct since the the young objects reachable from the newly-tenured object won't be marked in the young collection. That is why TOC then traces this newly-tenured object, which is
44.
by DblPlusUngood 10y ago
Indeed, as you say, write barriers precisely identify old-to-young pointers at the time of the write. But most collectors defer tracing and track this old-to-young pointer in a card-table, which results in lost precision i.e. now the collec
45.
by DblPlusUngood 10y ago
It sounds you like you asking for more toy OSes. Supporting POSIX is necessary if the designer wants the OS to run real software.
46.
by DblPlusUngood 10y ago
Interesting. The transactional hypothesis sounds like a refinement of the generational hypothesis. Seems like the main advantage of this transaction oriented collector over a typical generational collector is that it precisely identifies th
47.
by DblPlusUngood 10y ago
Here are even more names for this fallacy: tu quoque and whataboutism.
48.
by DblPlusUngood 10y ago
I would be much more excited about contraptions that were more obviously useful and less about providing a special "experience".
49.
by DblPlusUngood 10y ago
Ah, the classic false equivalence argument. You can expect at least one in any thread criticizing any country that isn't the USA!
50.
by DblPlusUngood 10y ago
Synchronous systems have the same problems you describe in your first paragraph, but worse (they tolerate less failures), so I'm not sure what you're trying to say. I don't buy the rest of your post for two reasons. First, pa
51.
by DblPlusUngood 10y ago
What exactly do you mean by "synchronous"? Do you have a particular system in mind? If you mean "block waiting for all replicas to respond", then the failure mode is quite different from Paxos. I don't know of one s
52.
by DblPlusUngood 10y ago
If you don't care about tolerating a single failure, then yes, pretending the network is synchronous can simplify your system.
53.
by DblPlusUngood 10y ago
I find it extremely amusing that after going through all the trouble of building the malware+infrastructure to sell keys, the authors couldn't be troubled to write the 5 lines of assembly code to enter protected mode. You can even leav
54.
by DblPlusUngood 11y ago
Hardware support for tracing branches is useful when the profiler cannot unwind the stack of the program being profiled (like when the binary is stripped and stack frames have been optimized out).
55.
by DblPlusUngood 11y ago
As a longtime OpenBSD misc reader, it took me a few minutes before I became convinced that the OP was joking.
56.
by DblPlusUngood 11y ago
These are a lot of fun! The doom marine in me demands a poster for Phobos!
57.
by DblPlusUngood 11y ago
It is both terrifying and amusing that rm'ing files in /sys can brick my Linux machine. I find it even more worrisome that some compare this mistake to accidental clobbering of /dev/sd?.
58.
by DblPlusUngood 11y ago
Here's another story: I was optimizing the performance of a small, in-house x86_64 OS on a specific benchmark. I spent many months finding and removing/improving bottlenecks. Once the performance was similar to competing OSes, the
59.
by DblPlusUngood 11y ago
For your enjoyment, a screencap of UEFI dumping core on a fancy Dell "server class" machine during bootup: http://i.imgur.com/YpOQXet.jpg Work required that I restarted this machine frequently -- it would fault du
60.
by DblPlusUngood 11y ago
I agree that Paxos is much simpler than many people apparently think. It certainly didn't help that the original paper is almost completely useless for learning Paxos. I highly recommend that anyone interesting in learning Paxos study

More ›