From: Antony Suter <sutera@internode.on.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.5-rc3-as1 patchset, cks5.2, cfq, aa1, and some wli
Date: Fri, 02 Apr 2004 18:21:25 +1000 [thread overview]
Message-ID: <1080894085.22675.0.camel@hikaru.lan> (raw)
Here is an update to my tidy set of patches. I was a fan of WLI's
patchset until he discontinued it in the 2.6.0-test era. They were a
small set of patches with performance improvements for laptops and NUMA
machines amongst others... (wish I had a laptop NUMA machine *cough*).
Some of those patches are now in the kernel proper. Some others have
been updated and are found elsewhere, like the objrmap series can be
found in Andrea Archangeli's -aa series. I'm starting to add some of the
other patches from WLI's last release, depending on my abolity to
resolve rejections. The numbers relate directly to those from
linux-2.6.0-test11-wli-1.tar.bz2
Patches were applied in the following order:
- Con Kolivas' new starcase cpu scheduler patch 5.2
- Jens Axboe's cfq io scheduler
- Andrea Archangeli's 2.6.5-rc3-aa2.bz2
< from linux-2.6.0-test11-wli-1 >
- #17 convert copy_strings() to use kmap_atomic() instead of kmap()
- #19 node-local i386 per_cpu areas
- #22 increase static vfs hashtable and VM array sizes
- #24 /proc/ BKL gunk plus page wait hashtable sizing adjustment
- #25 invalidate_inodes() speedup
Linqs:
http://www.users.on.net/sutera/2.6.5-rc3-as1.patch.gz
http://www.users.on.net/sutera/2.6.5-rc3-as1.patch.gz.sign
Note that to use the cfq scheduler to need to add "elevator=cfq" to your
kernel command line. This is usually done in your lilo or grub (or
equivalent) config.
--
- Antony Suter (sutera internode on net) "Bonta"
- "...through shadows falling, out of memory and time..."
next reply other threads:[~2004-04-02 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 8:21 Antony Suter [this message]
2004-04-02 10:14 ` 2.6.5-rc3-as1 patchset, cks5.2, cfq, aa1, and some wli William Lee Irwin III
2004-04-02 16:43 ` Antony Suter
2004-04-02 23:44 ` 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=1080894085.22675.0.camel@hikaru.lan \
--to=sutera@internode.on.net \
--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