From: William Lee Irwin III <wli@holomorphy.com>
To: badari <pbadari@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm mailing list <linux-mm@kvack.org>,
Andrew Morton <akpm@digeo.com>
Subject: Re: TASK_UNMAPPED_BASE & stack location
Date: Fri, 25 Apr 2003 16:58:43 -0700 [thread overview]
Message-ID: <20030425235843.GU8978@holomorphy.com> (raw)
In-Reply-To: <3EA9CA25.E140A02C@us.ibm.com>
On Fri, Apr 25, 2003 at 04:52:05PM -0700, badari wrote:
> Only problem with moving TASK_UNMAPPED_BASE right above
> text would be - limiting the malloc() space. malloc() is clever enough
> to mmap() and do the right thing. Once I moved TASK_UNMAPPED_BASE
> to 0x10000000 and I could not run some of the programs with large
> data segments.
> Moving stacks below text would be tricky. pthread library knows
> the placement of stack. It uses this to distinguish between
> threads and pthreads manager.
> I don't know what other librarys/apps depend on this kind of stuff.
STACK_TOP is easy to change to see what goes wrong; it's a single
#define in include/asm-i386/a.out.h
Someone should spin it up and see how well pthreads copes.
-- wli
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: badari <pbadari@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm mailing list <linux-mm@kvack.org>,
Andrew Morton <akpm@digeo.com>
Subject: Re: TASK_UNMAPPED_BASE & stack location
Date: Fri, 25 Apr 2003 16:58:43 -0700 [thread overview]
Message-ID: <20030425235843.GU8978@holomorphy.com> (raw)
In-Reply-To: <3EA9CA25.E140A02C@us.ibm.com>
On Fri, Apr 25, 2003 at 04:52:05PM -0700, badari wrote:
> Only problem with moving TASK_UNMAPPED_BASE right above
> text would be - limiting the malloc() space. malloc() is clever enough
> to mmap() and do the right thing. Once I moved TASK_UNMAPPED_BASE
> to 0x10000000 and I could not run some of the programs with large
> data segments.
> Moving stacks below text would be tricky. pthread library knows
> the placement of stack. It uses this to distinguish between
> threads and pthreads manager.
> I don't know what other librarys/apps depend on this kind of stuff.
STACK_TOP is easy to change to see what goes wrong; it's a single
#define in include/asm-i386/a.out.h
Someone should spin it up and see how well pthreads copes.
-- wli
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-04-25 23:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 20:32 TASK_UNMAPPED_BASE & stack location Martin J. Bligh
2003-04-25 20:32 ` Martin J. Bligh
2003-04-25 21:01 ` H. Peter Anvin
2003-04-25 21:10 ` Martin J. Bligh
2003-04-25 21:12 ` H. Peter Anvin
2003-04-25 22:02 ` Timothy Miller
2003-04-25 22:06 ` Martin J. Bligh
2003-04-25 23:15 ` H. Peter Anvin
2003-04-25 23:19 ` Martin J. Bligh
2003-04-26 0:11 ` H. Peter Anvin
2003-04-26 0:42 ` Hugh Dickins
2003-04-26 5:15 ` Martin J. Bligh
2003-04-26 10:40 ` jlnance
2003-04-26 15:39 ` Martin J. Bligh
2003-04-25 23:52 ` badari
2003-04-25 23:52 ` badari
2003-04-25 23:58 ` William Lee Irwin III [this message]
2003-04-25 23:58 ` William Lee Irwin III
2003-04-26 14:37 ` Rik van Riel
2003-04-26 14:37 ` Rik van Riel
2003-04-26 15:03 ` William Lee Irwin III
2003-04-26 15:03 ` William Lee Irwin III
[not found] <20030425204012$4424@gated-at.bofh.it>
2003-04-25 21:54 ` Andi Kleen
2003-04-25 22:06 ` William Lee Irwin III
2003-04-25 22:10 ` Martin J. Bligh
[not found] <20030425220018$6219@gated-at.bofh.it>
[not found] ` <20030425220018$76b1@gated-at.bofh.it>
[not found] ` <20030425225007$3fae@gated-at.bofh.it>
2003-04-25 22:58 ` Andi Kleen
2003-04-25 23:13 ` Hui Huang
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 23:02 Chuck Ebbert
2003-04-25 23:02 Chuck Ebbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030425235843.GU8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=pbadari@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.