From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: pgcl-2.5.64-[12]
Date: Wed, 5 Mar 2003 08:23:49 -0800 [thread overview]
Message-ID: <20030305162349.GF1399@holomorphy.com> (raw)
pgcl-2.5.64-1 includes the mprotect() fix from 2.5.63-based patches,
as well as an initial attempt at restoring swap functionality.
pgcl-2.5.64-2 fixes up the initial attempt at swapping so it actually
passes touch testing. Whether shmem.c handles this properly is
uncertain, but nothing obvious stands out as being in need of repair.
I bumped down PAGE_SIZE to 32K, 64K appeared to trigger issues with
qlogicisp.c on NUMA-Q. That may or may not eventually get fixed. It'd
certainly be interesting to go beyond the limits of the 2.4 patch.
Dealing with q->max_sectors*512 < PAGE_SIZE in a generic fashion looks
painful, and the driver is crusty, so swapping hardware sound good.
If this really holds up and there aren't enough fs or driver issues
to keep me occupied I might actually start dealing with performance
issues wrt. fragmentation of anonymous memory and L3 pagetables.
(Well, they're L2 pagetables in the nomenclature starting at L0.)
As usual, available from:
ftp://ftp.kernel.org/pub/linux/kernel/people/wli/vm/pgcl/
-- wli
reply other threads:[~2003-03-05 16:13 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=20030305162349.GF1399@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