Linux-kernel mailing list archive 2000-26,: Re: vmalloc() in interrupt context

# Re: vmalloc() in interrupt context

Alexander Viro (viro@math.psu.edu)
Tue, 27 Jun 2000 12:15:30 -0400 (EDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Manfred Spraul: "Re: closefd: closes a file of any process"
- Previous message: James Tunnicliffe: "2.4.0-test2 default config problem"

On Tue, 27 Jun 2000, Amit Dror wrote:

> Hi,
>
> I have a kernel driver that needs to dynamically allocate large amounts of
> memory in interrupt context.
>
> I can't use kmalloc(GFP_ATOMIC) or get_free_pages(GFP_ATOMIC) since they are
> limited to 131056 bytes.

Let me get it straight: you want atomic allocation of what, at least
256Kb? In interrupt context, of all places? Wow.

> I can't allocate the memory at the device initialization because the driver
> is a loadable module and is not compiled into the kernel.

Oh, yes, you can - module_init() is your friend.

-
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: Manfred Spraul: "Re: closefd: closes a file of any process"
- Previous message: James Tunnicliffe: "2.4.0-test2 default config problem"