From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: pgcl-2.5.66-1
Date: Tue, 25 Mar 2003 04:07:42 -0800 [thread overview]
Message-ID: <20030325120742.GP1232@holomorphy.com> (raw)
(1) add a CONFIG_PAGE_CLUSTER config option for i386.
(2) add stubs for MMUPAGE_* and PAGE_MMU* for non-i386
(3) fix up a do_page_cache_readahead() call in filemap_populate()
(4) fix up other file offset calculations surrounding the filepte merge
(5) sunrpc request buffer sizing fix from zwane
(6) make do_anonymous_page() less broken for x86 (but still nonportable)
do_wp_page() and other fault handler antifragmentation heuristics are
still underway. Once they're actually working and pagetable fragmentation
is fixed, some abstraction can be filtered out for the fault handlers'
needs and cleanups begin.
I'll reiterate for those who forgot the original announcement: this
patch is a WIP and it's not in yet in a state where the faint of heart
will be prepared to run it. Send pgcl bugreports as either followups to
my announcements or directly to me to avoid confusion regardless of
what subsystem they affect or who maintains the affected code.
Available from:
ftp://ftp.kernel.org/pub/linux/kernel/people/wli/vm/pgcl/
-- wli
reply other threads:[~2003-03-25 11:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030325120742.GP1232@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