From: Craig Kulesa <ckulesa@as.arizona.edu>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Steven Cole <elenstev@mesatop.com>,
William Lee Irwin III <wli@holomorphy.com>,
Steven Cole <scole@lanl.gov>,
Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] move slab pages to the lru, for 2.5.27
Date: Thu, 25 Jul 2002 05:00:15 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.44.0207241931060.17413-100000@loke.as.arizona.edu> (raw)
In-Reply-To: <200207242012.59150.tomlins@cam.org>
On Wed, 24 Jul 2002, Ed Tomlinson wrote:
> This patch fixes the SMP problems for Steve.
Good sleuthing! Glad to hear this seems to solve the bizarre SMP
out-of-memory problems. However, you should know that there *might* still
be demons lurking about.
I still have problems with 2.5.27-rmap-slablru with CONFIG_SMP booting on
a UP laptop, when 2.5.27-rmap (the big rmap patch) works fine in SMP mode.
I have spinlock debugging turned on and get oopses with modprobe trying to
load the rtc module. It fails this test in include/asm/spinlock.h:
#ifdef CONFIG_DEBUG_SPINLOCK
if (lock->magic != SPINLOCK_MAGIC)
BUG();
Modprobe also traps itself in infinite loops trying to load unix.o for
net-pf-1. Eeeks. I'll test on other UP boxes in SMP mode and see if I
can trigger anything.
For now, I've applied Ed's patch and tested that it doesn't cause any
problems for UP behavior, so I added it to the patch queue against 2.5.27
and is included in the rmap patches for 2.5.28, which you can download:
http://loke.as.arizona.edu/~ckulesa/kernel/rmap-vm/2.5.28/
The only new change for 2.5.28 is fixing software suspend to work
with the full rmap patch. I tested swsusp with 2.5.28-rmap-slablru, and
it's very cool. :)
Although I suspect SMP folks will have their hands busy with *other*
things in 2.5.28, (!!) more SMP feedback regarding slab-on-LRU would be
most helpful!
Thanks,
Craig Kulesa
--
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/
next parent reply other threads:[~2002-07-25 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200207242012.59150.tomlins@cam.org>
2002-07-25 12:00 ` Craig Kulesa [this message]
[not found] <200207210933.01211.tomlins@cam.org>
2002-07-21 21:24 ` Craig Kulesa
2002-07-21 23:15 ` Ed Tomlinson
2002-07-21 11:24 Craig Kulesa
2002-07-21 21:31 ` William Lee Irwin III
2002-07-22 7:08 ` Craig Kulesa
2002-07-22 18:54 ` Steven Cole
2002-07-22 22:21 ` William Lee Irwin III
2002-07-22 22:36 ` Craig Kulesa
2002-07-23 4:36 ` William Lee Irwin III
2002-07-23 14:31 ` Steven Cole
2002-07-24 20:28 ` Steven Cole
2002-07-24 21:02 ` Steven Cole
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=Pine.LNX.4.44.0207241931060.17413-100000@loke.as.arizona.edu \
--to=ckulesa@as.arizona.edu \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=scole@lanl.gov \
--cc=tomlins@cam.org \
--cc=wli@holomorphy.com \
/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