Thus spake Kamal R Prasad ("KRP> ") sometime May 2003!...

KRP> > The big problem with the "malloc in an area" stuff you're talking about
KRP> is
KRP> > that it's a cooperative thing, yet we're talking about an uncooperative
KRP> > problem. :-)
KRP>
KRP> if there is a framework for driver writers to malloc() from a seperate
KRP> pool,
KRP> bad programming will be taken care of by the bounds checks.
KRP>

Do we want "bad programming" to make it into the kernel in the first place?


				--*greywolf;
--
NetBSD: Choose Your Own Slogan.