From: Eric Whiting <ewhiting@amis.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: -mmX 4G patches feedback
Date: Mon, 05 Apr 2004 15:35:23 -0600 [thread overview]
Message-ID: <4071D11B.1FEFD20A@amis.com> (raw)
In-Reply-To: 20040405174616.GH2234@dualathlon.random
Andrea Arcangeli wrote:
>
> On Mon, Apr 05, 2004 at 10:36:58AM -0600, Eric Whiting wrote:
> > The 4G/4G patch is still useful for me -- although 64bit linux (x86_64) is the
> > best 'real' long-term solution to large memory jobs.
>
> what's your primary limitation? physical memory or virtual address
> space? if it's physical memory go with 2.6-aa and it'll work fine up to
> 32G boxes included at full cpu performance.
4G of virtual address is what we need. Virtual address space is why the -mmX
4G/4G patches are useful. In this application it is single processes (usually
running one at a time) that need more than 3G of RAM.
> if it's virtual address space and you've not much more than 4G of ram
> 3.5:1.5 usually works fine, and againt you'll run at full cpu
> performance.
3.5:1.5 appears to be a 2.4.x kernel patch only right?
next prev parent reply other threads:[~2004-04-05 23:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 16:36 -mmX 4G patches feedback Eric Whiting
2004-04-05 17:46 ` Andrea Arcangeli
2004-04-05 21:35 ` Eric Whiting [this message]
2004-04-05 22:16 ` Andrea Arcangeli
2004-04-06 11:55 ` -mmX 4G patches feedback [numbers: how much performance impact] Ingo Molnar
2004-04-06 14:49 ` Eric Whiting
2004-04-06 15:59 ` Andrea Arcangeli
2004-04-06 16:13 ` Arjan van de Ven
2004-04-06 16:39 ` Andrea Arcangeli
2004-04-06 17:24 ` Ingo Molnar
2004-04-06 17:57 ` Andrea Arcangeli
2004-04-07 22:54 ` Martin J. Bligh
2004-04-07 22:50 ` Andrea Arcangeli
2004-04-06 19:25 ` Ingo Molnar
2004-04-06 20:25 ` Andrea Arcangeli
2004-04-07 6:03 ` Andrea Arcangeli
2004-04-07 6:46 ` Ingo Molnar
2004-04-07 7:23 ` Andrea Arcangeli
2004-04-07 8:23 ` Ingo Molnar
2004-04-07 21:35 ` Andrea Arcangeli
2004-04-07 17:27 ` Andrea Arcangeli
2004-04-07 7:25 ` Ingo Molnar
2004-04-07 21:39 ` Andrea Arcangeli
2004-04-07 22:58 ` Martin J. Bligh
2004-04-07 23:01 ` Andrea Arcangeli
2004-04-07 23:21 ` Martin J. Bligh
2004-04-07 23:18 ` Andrea Arcangeli
2004-04-07 23:34 ` Martin J. Bligh
2004-04-08 0:18 ` Andrea Arcangeli
2004-04-08 6:24 ` Martin J. Bligh
2004-04-08 21:59 ` Andrea Arcangeli
2004-04-08 22:19 ` Martin J. Bligh
2004-04-08 22:19 ` Andrea Arcangeli
2004-04-08 23:14 ` Martin J. Bligh
2004-04-08 23:22 ` Andrea Arcangeli
2004-04-08 23:42 ` Martin J. Bligh
2004-04-08 23:49 ` Andrea Arcangeli
2004-04-07 21:19 ` -mmX 4G patches feedback Martin J. Bligh
2004-04-07 21:49 ` Andrea Arcangeli
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=4071D11B.1FEFD20A@amis.com \
--to=ewhiting@amis.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.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 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.