From: "Dan Noé" <dpn@isomerica.net>
To: David Newall <davidn@davidnewall.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Rafal Wijata <devnull@wijata.com>,
linux-kernel@vger.kernel.org
Subject: Re: Odd swapping issue
Date: Wed, 23 Jul 2008 22:20:48 -0400 [thread overview]
Message-ID: <4887E700.6060602@isomerica.net> (raw)
In-Reply-To: <4887A000.30605@davidnewall.com>
David Newall wrote:
> Peter Zijlstra wrote:
>> 16g ram on a 32bit kernel is stretching it... may I suggest running a
>> 64bit kernel?
>>
>
> Is it? Do we expect that behaviour with so much RAM?
The memory must be mapped into the 4GB (32-bit) virtual address space to
be used. Having this much memory on a system with 32 bit pointers leads
to a lot of VM overhead and strange behavior.
Cheers,
Dan
--
/--------------- - - - - - -
| Dan Noé
| http://isomerica.net/~dpn/
next prev parent reply other threads:[~2008-07-24 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 16:53 Odd swapping issue Rafal Wijata
2008-07-23 17:50 ` Peter Zijlstra
2008-07-23 21:17 ` David Newall
2008-07-24 2:20 ` Dan Noé [this message]
2008-07-24 6:39 ` Peter Zijlstra
2008-07-24 11:51 ` KOSAKI Motohiro
2008-07-24 13:45 ` Rafal Wijata (NULL)
2008-07-24 13:58 ` Peter Zijlstra
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=4887E700.6060602@isomerica.net \
--to=dpn@isomerica.net \
--cc=davidn@davidnewall.com \
--cc=devnull@wijata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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