[lkml]   [2003]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: TASK_UNMAPPED_BASE & stack location
    On Fri, 25 Apr 2003, Martin J. Bligh wrote:
    >> Is there any good reason we can't remove TASK_UNMAPPED_BASE, and just shove
    >> libraries directly above the program text? Red Hat seems to have patches to
    >> dynamically tune it on a per-processes basis anyway ...

    On Sat, Apr 26, 2003 at 10:37:11AM -0400, Rik van Riel wrote:
    > What could be done is leave the stack where it is, but have
    > malloc() space and mmap() space grow towards each other:
    > 0 3G
    > | |prog | malloc --> <-- mmap | stack |
    > The stack will get the stack size ulimit size and the space
    > between where malloc and mmap start should be about 2.7 GB.
    > That 2.7 GB will of course by divided between malloc and mmap,
    > but the division will be done dynamically based on whoever
    > needs the space. Much better than the current static 1:1.7
    > division...

    My internal proposals (backed by code) already include this in addition
    to relocating the stack (whose kernel side is trivial).

    -- wli
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:35    [W:0.019 / U:82.628 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site