From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@nl.linux.org>, kelly@nvidia.com
Cc: Linux MM <linux-mm@kvack.org>, linux-kernel@vger.rutgers.edu
Subject: Re: 1+ GB support (fwd)
Date: Fri, 14 Jan 2000 16:49:00 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.21.0001141635030.240-100000@alpha.random> (raw)
In-Reply-To: <Pine.LNX.4.10.10001140256150.13454-100000@mirkwood.dummy.home>
>
> I've read a bunch of linux news that says that the later kernels
>such as 2.3.35 can support more than 1gb of memory. I've put together a
>system with 4gb of RAM (dell 6300, 2x PIII 550 xeon CPUs) and can see that
2.2.14aa1 supports 4g of RAM on IA32 and 2Terabyte of RAM on alpha (wihout
per-process limit on alpha) with production quality. Apply the below patch
against 2.2.14 if you can't run an unstable tree.
ftp://ftp.*.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.2/2.2.14aa1.gz
>processes. However, I've been unable to malloc and use more than 1gb per
>process. Is this a limitation or am I doing something wrong? I've tried to
If you use 2.2.14aa1 you can apply these two incremental patches (they
should go on the top of 2.3.x as well) to allocate more ram per-process
(something like 3.5G). The two incremental patches are _not_ a good idea
if you need a large I/O cache (like for webservers). For scientific
application that only needs lots of RAM they should be fine.
ftp://ftp.*.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.2.14/bigmem-large-mapping-1.gz
ftp://ftp.*.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.2.14/patches/v2.2/2.2.14/bigmem-large-task-1.gz
Andrea
--
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.nl.linux.org/Linux-MM/
prev parent reply other threads:[~2000-01-14 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-14 1:56 Rik van Riel
2000-01-14 15:49 ` Andrea Arcangeli [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=Pine.LNX.4.21.0001141635030.240-100000@alpha.random \
--to=andrea@suse.de \
--cc=kelly@nvidia.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.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