From: Ed Tomlinson <tomlins@cam.org>
To: Andrew Morton <akpm@zip.com.au>, Craig Kulesa <ckulesa@as.arizona.edu>
Cc: linux-mm@kvack.org
Subject: Re: slablru for 2.5.32-mm1
Date: Fri, 6 Sep 2002 07:39:27 -0400 [thread overview]
Message-ID: <200209060739.27058.tomlins@cam.org> (raw)
In-Reply-To: <3D783156.68A088D1@zip.com.au>
On September 6, 2002 12:38 am, Andrew Morton wrote:
> Craig Kulesa wrote:
> > Ed Tomlinson wrote:
> > >> Andrew Morton wrote:
> > >>
> > >> The patch does a zillion BUG->BUG_ON conversions in slab.c, which is a
> > >> bit unfortunate, because it makes it a bit confusing to review. Let's
> > >> do that in a standalone patch next time ;)
> > >
> > > Yes. I would have left the BUG_ONs till later. Craig thought
> > > otherwise. I do agree two patches would have been better.
> >
> > I agree also. I never imagined that patch would make it up the ladder
> > before the BUG_ON's changes got split out into a separate patch. Sorry!
> > So... since I introduced the BUG_ON's, I thought I should clean it up.
> >
> > This is mostly for Ed and Andrew, but at:
> > http://loke.as.arizona.edu/~ckulesa/kernel/rmap-vm/2.5.33/
> >
> > you can get a copy of Andrew's slablru.patch from the 2.5.33-mm3 series
> > where I have altered fs/dcache.c and mm/slab.c (whose patches otherwise
> > apply cleanly to vanilla 2.5.33) to remove the BUG_ON changes. It does
> > reduce the size of the patch, and improves its readability considerably.
> > Hope that helps.
>
> Thanks. This patch is in Ed's hands at present - his call.
Craig, Andrew wants to see if we can get something similar to slablru without
using the lru. Think its possible, its about half coded. He also wants to
eliminate the 'lazy' release of slab pages. The bottom line is that slablru
is getting rewritten.
Do you have the BUGON changes in a patch all by themselves?
Ed
--
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 prev parent reply other threads:[~2002-09-06 11:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 4:07 Craig Kulesa
2002-09-06 4:24 ` Robert Love
2002-09-08 21:43 ` Daniel Phillips
2002-09-09 4:36 ` Robert Love
2002-09-09 5:10 ` Daniel Phillips
2002-09-06 4:38 ` Andrew Morton
2002-09-06 11:39 ` Ed Tomlinson [this message]
2002-09-06 18:57 ` Craig Kulesa
-- strict thread matches above, loose matches on Subject: below --
2002-08-28 22:11 Ed Tomlinson
2002-08-26 22:09 MM patches against 2.5.31 Ed Tomlinson
2002-08-26 23:58 ` Andrew Morton
2002-08-28 17:06 ` slablru for 2.5.32-mm1 Ed Tomlinson
2002-08-28 21:24 ` Andrew Morton
2002-08-28 22:23 ` Rik van Riel
2002-09-02 5:26 ` Andrew Morton
2002-09-02 15:00 ` Ed Tomlinson
2002-09-02 18:35 ` Andrew Morton
2002-09-02 19:09 ` Ed Tomlinson
2002-09-02 19:51 ` Andrew Morton
2002-09-02 6:50 ` Andrew Morton
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=200209060739.27058.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=akpm@zip.com.au \
--cc=ckulesa@as.arizona.edu \
--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