Using something like efence for such a thing is totally out of the question
right now, because if that overrun shows up after an hour of heavy use
under normal conditions, or if the code is trying to talk to real-world
things, the slowdown is so bad that the program is unusable, which means
that I cannot find the bug. (This has already happened to me.)
Others have remarked that persistent or distributed object storage ideas are
similarly affected.
Returning to 2.0 is NOT a viable option. Thus, I'd like to ask you to put
the AVL code back in. Thanks.
-- Matthias Urlichs | noris network GmbH | smurf@noris.de The quote was selected randomly. Really. | http://www.noris.de/~smurf/-- There's always the temptation to let other people think you're normal.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/faq.html