From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: Re: pgcl-2.5.68-1
Date: Tue, 22 Apr 2003 06:19:14 -0700 [thread overview]
Message-ID: <20030422131914.GE8931@holomorphy.com> (raw)
In-Reply-To: <20030422122747.GD8931@holomorphy.com>
On Tue, Apr 22, 2003 at 05:27:47AM -0700, William Lee Irwin III wrote:
> Results:
[...]
> HighTotal: 65198080 kB
> HighFree: 65131968 kB
> LowTotal: 751872 kB
> LowFree: 708480 kB
[...]
> LowFree remains above 700MB, as compared to under 200MB on mainline.
The point of the tree (I guess it's big enough to call a tree instead
of a patch) being, from the POV of my funding sources etc., that 64GB
i386 has significant amounts of lowmem pressure alleviated and so the
machines are actually able to support various workloads for which they
were intended. If you've got >= 16GB of highmem, you should be
extremely interested in this patch.
It also increases maximum fs blocksize, which was its original purpose
as it was conceived by Hugh Dickins in his 2.4.6/2.4.7 patches (and his
2.4.x implementation was in many ways superior to my own).
-- wli
next prev parent reply other threads:[~2003-04-22 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 12:27 pgcl-2.5.68-1 William Lee Irwin III
2003-04-22 13:19 ` William Lee Irwin III [this message]
2003-04-28 1:25 ` pgcl-2.5.68-1 William Lee Irwin III
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=20030422131914.GE8931@holomorphy.com \
--to=wli@holomorphy.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox