News for hackers. Stuff that matters.
Re:RethinkDB internals: handling stack overflow on custom st... by cperciva on Friday December 31, 2010 @05:04AM (#2055033)
I don't necessarily disagree with you, but I feel like your arguments address semantics/linguistics and not the actual issue.

It might be that, yes. But as a philosophy professor of my acquaintance likes to remark, "clear thinking requires clear language" (the irony of this phrase coming from a philosopher's mouth seems to be lost on him). Using unclear language both misleads the audience and makes it unclear whether the speaker understands what he's talking about.

(I find the same is true of code -- the clarity of some code seems very highly correlated with how well its author understands the problem space in question.)

Between us we're using three different definitions of "stack size" -- the size of the actual stack, the amount of RAM allocated, and the amount of VM space allocated; needless to say, I think the first definition makes the most sense. ;-)

When we get the chance we'll post benchmarks between GNU Pth, NPTL, and our coroutine implementation.

I recommend trying other operating systems too. Linux is famously bad at threading, and only survives in benchmarks because most applications which run on Linux are equally bad in how they use threads. What you really want (and seem to be implementing) is an M:N threading system, which is considerably more performant than either 1:1 or M:1.

Re:RethinkDB internals: handling stack overflow on custom st... by coffeemug on Friday December 31, 2010 @05:22AM (#2055065)
But as a philosophy professor of my acquaintance likes to remark, "clear thinking requires clear language"

I think you need to balance that with taking some shortcuts, or you'll never get to the essence (or at least your readers won't).