From: "Martin Schlemmer [c]" <azarah@nosferatu.za.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2-mm2 [u]
Date: Fri, 24 Sep 2004 02:53:58 +0200 [thread overview]
Message-ID: <1095987238.11535.4.camel@nosferatu.lan> (raw)
In-Reply-To: <20040922131210.6c08b94c.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Wed, 2004-09-22 at 13:12 -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-rc2/2.6.9-rc2-mm2/
>
> - Added Bart's bk-ide-dev tree to the -mm external tree lineup.
>
> - Added Peter Williams' Single Priority Array (SPA) O(1) CPU Scheduler, aka
> the "zaphod" cpu scheduler.
>
> It has a number of tunables and lots of documentation - see the changelog
> entry in zaphod-scheduler.patch for details.
>
> - This kernel doesn't work on ia64 (instant reboot). But neither does
> 2.6.9-rc2, nor current Linus -bk. Is it just me?
>
> - Added the kexec-based crashdump code. This is the code which uses kexec
> to jump into a new mini-kernel when the main kernel crashes. Userspace code
> in that mini-kernel then dumps the main kernel's memory to disk. These new
> patches provide the bits and pieces which the mini-kernel needs to be able
> to get at the main kernel's memory.
>
> There seem to be no hints as to how to get all this working - that will
> come.
>
> - Found (and fixed) the bug which was causing those
> ext3-goes-readonly-under-load problems. It was in the new wait/wakeup code.
>
I have a p4 ht box at home (smp kernel with smt enabled), and with this
I seem to get zombie processes (nautilus a few times now).
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-24 1:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 20:12 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 20:48 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 20:54 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 21:05 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 20:55 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-22 20:59 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 21:04 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 21:10 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 21:02 ` 2.6.9-rc2-mm2 Stefan Seyfried
2004-09-22 22:27 ` 2.6.9-rc2-mm2 Peter Williams
2004-09-23 1:47 ` 2.6.9-rc2-mm2 Nuno Ferreira
2004-09-23 2:03 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-23 2:58 ` 2.6.9-rc2-mm2 Herbert Xu
2004-09-23 9:29 ` 2.6.9-rc2-mm2 Nuno Ferreira
2004-09-23 3:00 ` 2.6.9-rc2-mm2 Nick Piggin
2004-09-23 5:07 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 5:27 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 5:46 ` 2.6.9-rc2-mm2 Peter Williams
2004-09-23 6:01 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 13:15 ` 2.6.9-rc2-mm2 Vladimir Saveliev
2004-09-23 15:51 ` 2.6.9-rc2-mm2 (disable repacker) Mike Houston
2004-09-23 16:48 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 17:59 ` 2.6.9-rc2-mm2 Akinobu Mita
2004-09-24 0:53 ` Martin Schlemmer [c] [this message]
2004-10-02 7:44 ` 2.6.9-rc2-mm2 Jaakko Hyvätti
2004-10-02 7:49 ` 2.6.9-rc2-mm2 Andrew Morton
2004-10-02 18:21 ` 2.6.9-rc2-mm2 Jaakko Hyvätti
2004-10-08 11:24 ` 2.6.9-rc2-mm2 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=1095987238.11535.4.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=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