From: "H. Peter Anvin" <hpa@zytor.com>
To: Peter Rabbitson <rabbit@rabbit.us>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Terrible IO performance when using 4GB of RAM on a 32 bit machine
Date: Thu, 21 Jun 2007 12:26:57 -0700 [thread overview]
Message-ID: <467AD101.4020107@zytor.com> (raw)
In-Reply-To: <467AB4CF.7030904@rabbit.us>
Peter Rabbitson wrote:
>
> I have captured dmesg output without mem[5], with mem=3900M[6] and
> mem=2048M[7].
>
What does /proc/mtrr look like in the two cases?
-hpa
next prev parent reply other threads:[~2007-06-21 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 17:26 Terrible IO performance when using 4GB of RAM on a 32 bit machine Peter Rabbitson
2007-06-21 19:26 ` H. Peter Anvin [this message]
2007-06-21 23:02 ` Peter Rabbitson
[not found] <fa.8+Qu4ZH2B8PP3bRaZ5LNdUcsFIQ@ifi.uio.no>
[not found] ` <fa.X6rjOVHT6SoOzt6SHEJROeRgf98@ifi.uio.no>
[not found] ` <fa.qwrQSldd4OzDT6RgWE5P1BD9PJw@ifi.uio.no>
2007-06-22 0:00 ` Robert Hancock
2007-06-22 8:29 ` Peter Rabbitson
2007-06-22 14:36 ` Robert Hancock
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=467AD101.4020107@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabbit@rabbit.us \
/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;
as well as URLs for NNTP newsgroup(s).