Messages in this thread | | | Date | Fri, 25 Apr 2003 13:32:18 -0700 | From | "Martin J. Bligh" <> | Subject | TASK_UNMAPPED_BASE & stack location |
| |
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 ...
Moreover, can we put the stack back where it's meant to be, below the program text, in that wasted 128MB of virtual space? Who really wants > 128MB of stack anyway (and can't fix their app)?
I'm sure there's some horrible reason we can't do this ... would just like to know what it is. If it's "standards compilance" I don't really believe it - we don't comply with the standard now anyway ...
M.
PS. Motivation is creating large shmem segments for DBs. - 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/
| |