From: Andrew Morton <akpm@zip.com.au>
To: Ed Tomlinson <tomlins@cam.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: [PATCH] slablru for linux-2.5 bk tree
Date: Sat, 03 Aug 2002 20:17:10 -0700 [thread overview]
Message-ID: <3D4C9CB6.92504CF0@zip.com.au> (raw)
In-Reply-To: <200208031527.15093.tomlins@cam.org>
Ed Tomlinson wrote:
>
> Hi,
>
> Here the slablru patch ported to 2.5.30.
Ed, it's going to take some time/effort to get this shaken down
and into the tree, I expect. There's quite a bit banked up
at present.
I'll take care of any stability and performance stuff in slablru, but
the wider question is: what behaviour do we actually _want_ for slab
pages, and is this code delivering it? Need to think about that. But
we certainly can't do worse than we are at present ;)
I've merged your patch on top of the pagemap_lru_lock patches. A whole
bunch of nastiness went away because those patches allow us to take that
lock from interrupt context.
The locking in slab.c needs some going over - I think it's wrong from a
2.4 perspective: there's one ranking bug between pagemap_lru_lock and
the cachep->spinlock. I'd suggest that you change the 2.4 implementation
to just drop pagemap_lru_lock before calling from vmscan into
kmem_shrink_slab(). One thing will lead to another and the locking in slab
will get simpler. Just make the lru lock nest inside the cachep->spinlock.
The fiddled patch is at http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.30/
I'll read through it a bit more next week, give it a bit of testing.
Thanks.
--
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/
prev parent reply other threads:[~2002-08-04 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0207282324340.872-100000@home.transmeta.com>
[not found] ` <200208011942.49342.tomlins@cam.org>
[not found] ` <3D49C951.AB7C527E@zip.com.au>
2002-08-03 19:27 ` Ed Tomlinson
2002-08-03 20:43 ` Rik van Riel
2002-08-04 3:17 ` Andrew Morton [this message]
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=3D4C9CB6.92504CF0@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=tomlins@cam.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