From: Andrew Morton <akpm@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.0
Date: Wed, 17 Dec 2003 21:15:16 -0800 [thread overview]
Message-ID: <20031217211516.2c578bab.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0312171951030.5789@home.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
>
> Andrew has written up some caveats and pointers to information about 2.4.x
> vs 2.6.x changes, and I'll let him post that. Some known issues were not
> considered to be release-critical and a number of them have pending fixes
> in the -mm queue. Generally they just didn't have the kind of verification
> yet where I was willing to take them in order to make sure a fair 2.6.0
> release.
It's actually rather short because I started late. See below.
There are also the "must-fix" and "should-fix" lists of items which we have
identified as still on the 2.6 todo list. These are at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix/must-fix-7.txt and
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix/should-fix-7.txt
- The 2.6.0 kernel has undergone several weeks of stabilization and we
expect it to run well on server-class machines.
Desktops and laptops may have more trouble at this time because of the
much wider range of hardware and because of as-yet unimplemented fixes for
the hardware and BIOS bugs from which these machines tend to suffer.
During the 2.6.0 stabilization period a significant number of less
serious fixes have accumulated in various auxiliary kernel trees and these
shall be merged into the 2.6 stream after the 2.6.0 release. Many of these
fixes appear in Andrew Morton's "-mm" tree, at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/
- Please report any problems to the appropriate mailing list. If you do
not know which list to use, send the report to linux-kernel@vger.kernel.org
and it should reach the right person. Some active subsystem mailing lists
are:
linux1394-devel@lists.sourceforge.net
linux-xfs@oss.sgi.com
linux-acpi@intel.com
linux-scsi@vger.kernel.org
ext2-devel@lists.sourceforge.net
linux-usb-users@lists.sourceforge.net
Alternatively, kernel bug reports may be entered into the kernel bug
tracking system at http://bugme.osdl.org/
- There are significant changes in the module subsystem, the LVM (Device
Mapper) and RAID subsystems. Details about these and many other kernel
changes are presented in David Jones's kernel upgrade document at
http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt
Users who are testing 2.6 kernels for the first time should consult this
document.
- The ATA RAID drivers (eg the HighPoint RAID driver) have not been ported
to the new BIO code and are not available under the 2.6 kernel at this
time.
- cryptoloop doesn't work on highmem machines. Fixes exist in -mm and are
queued for 2.6.1.
- There are known performance problems with the default disk I/O scheduler
which show up when the workload is performing small, random reads and
writes (ie: database loads). Largely fixed in -mm.
In general, the "deadline" I/O scheduler is, and shall remain somewhat
faster than the default "anticipatory" I/O scheduler with these sorts of
workloads. Database admins should consider adding the "elevator=deadline"
kernel boot parameter.
- There are performance problems due to misbehaviour in the readahead code
which also impact database-style workloads. Fixed in -mm, queued for
2.6.1.
- There are a larger number of as-yet unmerged frame buffer driver fixes.
next prev parent reply other threads:[~2003-12-18 5:14 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 4:14 Linus Torvalds
2003-12-18 4:50 ` Jonathan Brown
2003-12-18 5:00 ` Gerardo Exequiel Pozzi
2003-12-18 5:05 ` Joshua Kwan
2003-12-18 5:07 ` Norberto Bensa
2003-12-18 5:15 ` Andrew Morton [this message]
2003-12-18 5:31 ` Jeff Garzik
2003-12-18 5:50 ` Trond Myklebust
2003-12-18 6:14 ` Andrew Morton
2003-12-18 6:41 ` Trond Myklebust
2003-12-18 9:12 ` ismail 'cartman' dönmez
2003-12-18 9:34 ` Greg KH
2003-12-18 9:48 ` Maciej Soltysiak
2003-12-18 9:59 ` Matt H.
2003-12-18 10:19 ` Jens Axboe
2003-12-18 11:00 ` Maciej Soltysiak
2003-12-18 10:43 ` Hans Reiser
2003-12-18 11:03 ` reiser4 in 2.6 was " Maciej Soltysiak
2003-12-18 11:42 ` Hans Reiser
2003-12-19 17:58 ` E. Gryaznova
2003-12-18 16:17 ` bill davidsen
2003-12-18 19:31 ` Hans Reiser
2003-12-18 19:42 ` Jens Axboe
2003-12-18 22:48 ` Ed Tomlinson
2003-12-19 3:42 ` Hans Reiser
2003-12-19 6:57 ` Jens Axboe
2003-12-18 9:17 ` Marcel Holtmann
2003-12-18 13:43 ` Joseph Pingenot
2003-12-18 16:22 ` Andrew Morton
2003-12-18 21:02 ` List of mailing lists (was Re: Linux 2.6.0) Rob Landley
2003-12-18 14:21 ` Linux 2.6.0 Michael Hunold
2003-12-18 19:45 ` MD Raid fixed? was: " Mike Fedyk
2003-12-18 21:49 ` Neil Brown
2003-12-18 5:48 ` Krishna Akella
2003-12-18 7:16 ` Gabor MICSKO
2003-12-18 7:25 ` Clemens Schwaighofer
2003-12-18 9:56 ` Andrew Walrond
2003-12-18 10:20 ` Carlos Jiménez
2003-12-18 12:34 ` iain d broadfoot
2003-12-19 2:18 ` Diskstats inconsistancy between 2.4.23 & 2.6 was: " Mike Fedyk
2003-12-19 2:32 ` William Lee Irwin III
2003-12-19 3:03 ` Mike Fedyk
2003-12-18 5:24 Shawn Starr
2003-12-18 18:12 (->surya<-)
2003-12-18 23:16 Jean Tourrilhes
2003-12-19 0:31 ` Martin Diehl
2003-12-19 1:01 ` Jean Tourrilhes
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=20031217211516.2c578bab.akpm@osdl.org \
--to=akpm@osdl.org \
--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
Powered by JetHome