RE: kmalloc()'ing greater than 128k

Lee Rhodes (LeeR@eicon.com)
Wed, 3 Nov 1999 07:58:44 -0500

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Biondi, Philippe: "exported kernel symbols"
Previous message: Theodore Y. Ts'o: "Re: vfork"

> could you try 2.2.13?
Whoops. I've been caught with egg on my face! Tracked the crawling down to
something which isn't related to memory at all! So you can disregard this
crawling behaviour that I speak of. It has been 'dealt with' :)

> i believe vmalloc()/vfree() is the best choice, as long as you are not
> doing this from IRQ handlers.
Absolutely. Thanks for the useful insight on the alternatives to
vmallocation.

Lee

-
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/

Next message: Biondi, Philippe: "exported kernel symbols"
Previous message: Theodore Y. Ts'o: "Re: vfork"