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

From: Grzegorz Jaskiewicz (gj@pointblue.com.pl)
Date: Mon Feb 03 2003 - 10:35:57 EST


On Mon, 2003-02-03 at 15:19, Arjan van de Ven wrote:
> > #include <linux/modversions.h>
> don't do that. ever.
why ?

> > #ifdef CONFIG_KMOD
> > #include <linux/kmod.h>
> > #endif
>
> bullshit ifdef's (and the surrounding code has a whole bunch too
this has been taken from first from edge module, just to put it into example ;)

> btw you do know you can't do vmalloc (or vfree) from interrupt context ?
> And that every vmalloc eats at minimum 8Kb of virtual memory space? Of
> which you can't count on having more than 64Mb on x86 ?
I didn't knew that. I have at least as i said 300 of those, if user
space software is doing something else. In practice i have around 30.
even if 1000 it gives 1000*8kb=8MB so it is not that bad. This mashine
has 128MB atleast.
Whatver, should i consider timer as interrupt too ?

-- 
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 Labs

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



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