| |||||||||||||
Fear of the voidFear of the voidPosted Jun 17, 2004 9:25 UTC (Thu) by jae (subscriber, #2369)Parent article: Fear of the void In the light of recent kernel vulns: How much performance does this suck, or rather, how much would it cost if the global allocator would support this scheme? If it's not too expensive (might well be, I don't read lkml), wouldn't it be better to use it and get a bit more safety into the kernel?
(Log in to post comments)
Fear of the void Posted Sep 11, 2004 9:29 UTC (Sat) by jbglaw (subscriber, #10406) [Link] Private data structures are mostly allocated at driver load or open time, so I guess there's not much of a performance penalty.
However, you need to keep the magic number around, too, so the kernel again gets a bit larger. You'd say this is unneeded bloat, since kernel code should be error free :-)
|
|||||||||||||