lkml.org 
[lkml]   [2003]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [BUG] vmalloc, kmalloc - 2.4.x
    From
    Date
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:32    [W:0.021 / U:178.768 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site