Re: [BUG] vmalloc, kmalloc - 2.4.x

From: Benjamin Herrenschmidt (benh@kernel.crashing.org)
Date: Mon Feb 03 2003 - 12:02:04 EST

Next message: Andrea Arcangeli: "Re: 2.4, 2.5: SMP race: __sync_single_inode vs. __mark_inode_dirty"
Previous message: Seamus: "CPU throttling??"
In reply to: Grzegorz Jaskiewicz: "Re: [BUG] vmalloc, kmalloc - 2.4.x"
Next in thread: Richard B. Johnson: "Re: [BUG] vmalloc, kmalloc - 2.4.x"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, 2003-02-03 at 16:40, Grzegorz Jaskiewicz wrote:
> On Mon, 2003-02-03 at 16:18, Alan Cox wrote:
>
> > Firstly vmalloc isnt permitted in interrupt context (use kmalloc with GFP_KERNEL),
> > although for such small chunks you might want to vmalloc a bigger buffer once
> > at startup.
> i've allso tried kmalloc with the same result.
> Also, in this example it is timer - module isn't cleanly wroted becouse
> it supose to be only an example.

I suppose you meant kmalloc with GFP_ATOMIC...

-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Andrea Arcangeli: "Re: 2.4, 2.5: SMP race: __sync_single_inode vs. __mark_inode_dirty"
Previous message: Seamus: "CPU throttling??"
In reply to: Grzegorz Jaskiewicz: "Re: [BUG] vmalloc, kmalloc - 2.4.x"
Next in thread: Richard B. Johnson: "Re: [BUG] vmalloc, kmalloc - 2.4.x"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Feb 07 2003 - 22:00:11 EST