From: Raymond Nijssen <raymond.nijssen@Magma-DA.COM>
To: linux-mm@kvack.org
Subject: Re: max memory limits ???
Date: Sat, 25 Nov 2000 02:45:05 -0800 (PST) [thread overview]
Message-ID: <200011251045.CAA07659@manet.magma-da.com> (raw)
In-Reply-To: <3A1BCC05.4080608@SANgate.com>; from gabriel@SANgate.com on Wed, Nov 22, 2000 at 03:37:09PM +0200
>Matti Aarnio <matti.aarnio@zmailer.org> wrote:
>On Wed, Nov 22, 2000 at 03:37:09PM +0200, BenHanokh Gabriel wrote:
>> can some1 explain the memory limits on the 2.4 kernel
>> - what is the limit for user-space apps ?
> At 32 bit systems: 3.5 GB with extreme tricks, 3 GB for more usual.
What are those tricks? Do they involve changing TASK_SIZE ?
And why do programs get mapped at 0x08000000 instead of 0x00001000 ?
This is wasting another 5% of the addressing space.
Please CC me on your reply.
Thanks,
-Raymond
--
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.eu.org/Linux-MM/
prev parent reply other threads:[~2000-11-25 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 13:37 BenHanokh Gabriel
2000-11-22 14:11 ` Matti Aarnio
2000-11-22 15:28 ` Stephen C. Tweedie
2000-11-25 10:45 ` Raymond Nijssen [this message]
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=200011251045.CAA07659@manet.magma-da.com \
--to=raymond.nijssen@magma-da.com \
--cc=linux-mm@kvack.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox