From: David Chinner <dgc@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Chinner <dgc@sgi.com>,
xfs-masters@oss.sgi.com,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, reiserfs-dev@namesys.com
Subject: Re: [xfs-masters] Re: [PATCH] Cleanup and kernelify shrinker registration (rc5-mm2)
Date: Wed, 4 Apr 2007 10:03:54 +1000 [thread overview]
Message-ID: <20070404000354.GA32597093@melbourne.sgi.com> (raw)
In-Reply-To: <20070403103627.de831e3e.akpm@linux-foundation.org>
On Tue, Apr 03, 2007 at 10:36:27AM -0700, Andrew Morton wrote:
> On Tue, 3 Apr 2007 22:37:06 +1000 David Chinner <dgc@sgi.com> wrote:
>
> > On Tue, Apr 03, 2007 at 05:18:25PM +1000, Rusty Russell wrote:
> > > On Mon, 2007-04-02 at 23:09 -0700, Andrew Morton wrote:
> > > This is not about efficiency. When have I *ever* posted optimization
> > > patches?
> > >
> > > This is about clarity. We have a standard convention for
> > > register/unregister. And they can't fail. Either of these would be
> > > sufficient to justify a change.
> > >
> > > Too many people doing cool new things in the kernel, not enough
> > > polishing of the crap that's already there 8(
> > >
> > > > But I think we need to weed that crappiness out of XFS first.
> >
> > Can anyone else see the contradiction in these statements?
> >
> > XFS's "crappiness" is a register/unregister interface. The only
> > reason it's being removed is because it's getting replaced with a
> > nearly identical register/unregister interface.
>
> Nope. XFS is introducing two new typedefs, one of which is identical to
> one which we already have and it has wrapper functions which do little more
> than add new names for existing stuff.
And the problem with that is? You haven't noticed this in the five
years it's been there providing XFS with a consistent shrinker
interface.....
FWIW, digging back into history, Rusty's first patch basically
brings use back to the same interface we had in 2.4. Here's
the 2.4 version of that function:
kmem_shaker_t
kmem_shake_register(kmem_shake_func_t sfunc)
{
kmem_shaker_t shaker = kmalloc(sizeof(*shaker), GFP_KERNEL);
if (!shaker)
return NULL;
memset(shaker, 0, sizeof(*shaker));
shaker->shrink = sfunc;
register_cache(shaker);
return shaker;
}
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-04-04 0:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 3:44 Rusty Russell
2007-04-03 3:47 ` Rusty Russell
2007-04-03 3:58 ` Andrew Morton
2007-04-03 4:45 ` Rusty Russell
2007-04-03 4:57 ` Andrew Morton
2007-04-03 5:44 ` [xfs-masters] " David Chinner
2007-04-03 6:01 ` Andrew Morton
2007-04-03 6:19 ` David Chinner
2007-04-04 0:30 ` Rusty Russell
2007-04-03 5:47 ` Rusty Russell
2007-04-03 6:09 ` Andrew Morton
2007-04-03 7:18 ` Rusty Russell
2007-04-03 12:37 ` [xfs-masters] " David Chinner
2007-04-03 17:36 ` Andrew Morton
2007-04-04 0:03 ` David Chinner [this message]
2007-04-03 9:57 ` Andi Kleen
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=20070404000354.GA32597093@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=reiserfs-dev@namesys.com \
--cc=xfs-masters@oss.sgi.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