From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: pgcl-2.5.64-[345]
Date: Mon, 10 Mar 2003 21:15:11 -0800 [thread overview]
Message-ID: <20030311051511.GM465@holomorphy.com> (raw)
pgcl-2.5.64-3:
(1) remove some debug checks from rmap and highmem functions
(2) mitigate anonymous page fragmentation in do_anonymous_page()
this heuristic is still not entirely effective
pgcl-2.5.64-4:
(1) edit all PTE's pointed at a given page at swap fault time
(2) comment some TODO items
(3) remove WARN_ON()'s triggered by PTE allocation fallback to lowmem
pgcl-2.5.64-5:
(1) re-sweep arch/i386/kernel/cpu/mtrr/ for PAGE_SIZE vs. MMUPAGE_SIZE
MTRR code basically wants MMUPAGE_SIZE in all cases
As usual, available from:
ftp://ftp.kernel.org/pub/linux/kernel/people/wli/vm/pgcl/
The fault-time antifragmentation heuristics here are largely ineffective.
Most of this will have to be revisited, but if you were seeing issues with
MTRR's or spurious WARN_ON()'s from PTE allocation fallback to ZONE_NORMAL,
these updates should help. Incremental atop prior 2.5.64 pgcl patches.
-- wli
next reply other threads:[~2003-03-11 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 5:15 William Lee Irwin III [this message]
2003-03-11 5:48 ` pgcl-2.5.64-[345] 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=20030311051511.GM465@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