From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [RFT] please test the big post-2.6.5 merge
Date: Tue, 13 Apr 2004 13:05:28 -0400 [thread overview]
Message-ID: <407C1DD8.5060909@pobox.com> (raw)
The snapshot 2.6.5-bk1 is out, and has a _ton_ of changes in it that
have been waiting to go upstream for several weeks. This snapshot
includes many more _major_ changes than most snapshots, so I wanted to
call special attention to it, and request testing and feedback from
linux-kernel denizens.
Changelog describing the 457 changes in this snapshot:
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.5-bk1.log
Patch:
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.5-bk1.bz2
Short, jgarzik-generated list of major changes that probably want testing:
* non-exec stack support
* much better block I/O unplugging (I/O scalability)
* laptop mode
* lots of VM work (often related to I/O or Hugh's rmap/anonvma stuff)
* 4K stacks
* updated software suspend
* early x86 boot changes
* several ext2/ext3/jbd improvements
* new "CFQ" I/O scheduler
* queue congestion hooks
* DM, MD fixes (some related to the queue congestion/unplugging changes)
* posix message queue work from Manfred
* lightweight auditing framework
* reiserfs fixes and features
* readahead tweaks and fixes
* writeback tweaks
* direct-IO and AIO fixes and speed-ups
* shrinkage from Matt Mackall's -tiny tree
* /dev/urandom scalability
* update slab for per-arch alignments
* initramfs fix
* knfsd fixes and updates
* nfs client fixes/updates
* pcmcia update
* SATA update
* selinux update
* v4l update
* various arch updates: H8300, s/390, ppc32, ppc64, x86-64, nommu, arm, ...
next reply other threads:[~2004-04-13 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 17:05 Jeff Garzik [this message]
2004-04-13 19:54 ` [RFT] please test the big post-2.6.5 merge cliff white
[not found] ` <0FFF7180-8D8F-11D8-BB04-000A9585C204@able.es>
2004-04-13 21:21 ` Jeff Garzik
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=407C1DD8.5060909@pobox.com \
--to=jgarzik@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.