From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Gerrit Huizenga <gh@us.ibm.com>,
William Lee Irwin III <wli@holomorphy.com>
Cc: "Reed, Timothy A" <timothy.a.reed@lmco.com>,
"Linux Kernel ML (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: High Mem Options
Date: Wed, 05 Mar 2003 13:34:22 -0800 [thread overview]
Message-ID: <655220000.1046900062@flay> (raw)
In-Reply-To: <E18qgAh-00033w-00@w-gerrit2>
> Ah, if you are referring to a number from me, that was with 2.4 and
> that number seemed high to me at the time. I don't believe that 10%
> *should* be the amount of degradation. But I don't have current numbers
> (that I can share, anyway ;-) that prove anything less than that.
>
> I expect that we'll be diving into this more over the next few months
> as we can generate some large workloads and find the cause of the
> degradation (and hopefully minimize it).
Would also be useful to measure the overhead on a machine with < 4Gb
of RAM ... otherwise you have two effects to deal with:
1. the PAE overhead.
2. The increase in RAM - more data to manage, and potential bounce-buffers.
M.
next prev parent reply other threads:[~2003-03-05 21:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 11:28 High Mem Options Reed, Timothy A
2003-03-05 12:11 ` Michael Vergoz
2003-03-05 13:36 ` Alan Cox
2003-03-05 12:49 ` Michael Vergoz
2003-03-05 12:57 ` William Lee Irwin III
2003-03-05 13:02 ` Michael Vergoz
2003-03-05 13:10 ` William Lee Irwin III
2003-03-09 2:41 ` Bill Davidsen
2003-03-05 14:21 ` Alan Cox
2003-03-05 12:26 ` William Lee Irwin III
2003-03-05 20:31 ` Gerrit Huizenga
2003-03-05 20:58 ` William Lee Irwin III
2003-03-05 21:11 ` Gerrit Huizenga
2003-03-05 21:34 ` Martin J. Bligh [this message]
2003-03-05 13:38 ` Alan Cox
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=655220000.1046900062@flay \
--to=mbligh@aracnet.com \
--cc=gh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=timothy.a.reed@lmco.com \
--cc=wli@holomorphy.com \
/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.