From: Andrew Morton <akpm@digeo.com>
To: lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: 2.5.44-mm4
Date: Wed, 23 Oct 2002 21:28:37 -0700 [thread overview]
Message-ID: <3DB776F5.C5AA1922@digeo.com> (raw)
url: http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.44/2.5.44-mm4/
Having a few stability problems so most of the new things have been
removed. Once this thing is working properly we can start moving
forward again.
If the people who had problem with -mm4 could please retest? If
problems remain, please try popping off shpte-ng.patch.
Also be suspicious of CONFIG_PREEMPT=y. For me, with preempt, smp
and spinlock debugging the kernel dies immediately doing an unlock
of already-unlocked kernel_flag when bringing up the first migration
thread. That's on base 2.5.44. May not be a preempt problem; could
be that preempt is simply exposing it.
+read-barrier-depends.patch
RCU fix
+deferred-lru-add-fix.patch
lru_cache_add fix
-for-each-cpu.patch
Dropped. Rusty has a different cpu iterator patch
-task-unmapped-base-fix.patch
Folded into ingo-mmap-speedup
-larger-cpu-masks.patch
-adam-loop.patch
-rcu-stats.patch
-generic-nonlinear-mappings-D0.patch
Over in experimental/
+md-01-driverfs-core.patch
+md-02-driverfs-topology.patch
+md-03-numa-meminfo.patch
+md-04-memblk_online_map.patch
+md-05-node_online_map.patch
The NUMA driverfs interfaces from Matt Dobson. Queued up in
experimental/ too. It all adds only a few hundred bytes to a
non-NUMA build.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
reply other threads:[~2002-10-24 4:28 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=3DB776F5.C5AA1922@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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