From: Andrew Morton <akpm@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, xfs-masters@oss.sgi.com,
reiserfs-dev@namesys.com
Subject: Re: [PATCH] Cleanup and kernelify shrinker registration (rc5-mm2)
Date: Mon, 2 Apr 2007 20:58:25 -0700 [thread overview]
Message-ID: <20070402205825.12190e52.akpm@linux-foundation.org> (raw)
In-Reply-To: <1175571885.12230.473.camel@localhost.localdomain>
On Tue, 03 Apr 2007 13:44:45 +1000 Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> I can never remember what the function to register to receive VM pressure
> is called. I have to trace down from __alloc_pages() to find it.
>
> It's called "set_shrinker()", and it needs Your Help.
>
> New version:
> 1) Don't hide struct shrinker. It contains no magic.
> 2) Don't allocate "struct shrinker". It's not helpful.
> 3) Call them "register_shrinker" and "unregister_shrinker".
> 4) Call the function "shrink" not "shrinker".
> 5) Rename "nr_to_scan" argument to "nr_to_free".
No, it is actually the number to scan. This is >= the number of freed
objects.
This is because, for better of for worse, the VM tries to balance the
scanning rate of the various caches, not the reclaiming rate.
> 6) Reduce the 17 lines of waffly comments to 10, and document the -1 return.
>
> Comments:
> 1) The comment in reiserfs4 makes me a little queasy.
I'm going to have to split this patch up into mainline-bit and reiser4-bit.
And that's OK (it's a regular occurrence). But never miss a chance to whine.
> 2) The wrapper code in xfs might no longer be needed.
> 3) The placing in the x86-64 "hot function list" for seems a little
> unlikely. Clearly, Andi was testing if anyone was paying attention.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, xfs-masters@oss.sgi.com,
reiserfs-dev@namesys.com
Subject: Re: [PATCH] Cleanup and kernelify shrinker registration (rc5-mm2)
Date: Mon, 2 Apr 2007 20:58:25 -0700 [thread overview]
Message-ID: <20070402205825.12190e52.akpm@linux-foundation.org> (raw)
In-Reply-To: <1175571885.12230.473.camel@localhost.localdomain>
On Tue, 03 Apr 2007 13:44:45 +1000 Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> I can never remember what the function to register to receive VM pressure
> is called. I have to trace down from __alloc_pages() to find it.
>
> It's called "set_shrinker()", and it needs Your Help.
>
> New version:
> 1) Don't hide struct shrinker. It contains no magic.
> 2) Don't allocate "struct shrinker". It's not helpful.
> 3) Call them "register_shrinker" and "unregister_shrinker".
> 4) Call the function "shrink" not "shrinker".
> 5) Rename "nr_to_scan" argument to "nr_to_free".
No, it is actually the number to scan. This is >= the number of freed
objects.
This is because, for better of for worse, the VM tries to balance the
scanning rate of the various caches, not the reclaiming rate.
> 6) Reduce the 17 lines of waffly comments to 10, and document the -1 return.
>
> Comments:
> 1) The comment in reiserfs4 makes me a little queasy.
I'm going to have to split this patch up into mainline-bit and reiser4-bit.
And that's OK (it's a regular occurrence). But never miss a chance to whine.
> 2) The wrapper code in xfs might no longer be needed.
> 3) The placing in the x86-64 "hot function list" for seems a little
> unlikely. Clearly, Andi was testing if anyone was paying attention.
--
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-03 3:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 3:44 [PATCH] Cleanup and kernelify shrinker registration (rc5-mm2) Rusty Russell
2007-04-03 3:44 ` Rusty Russell
2007-04-03 3:47 ` Rusty Russell
2007-04-03 3:47 ` Rusty Russell
2007-04-03 3:58 ` Andrew Morton [this message]
2007-04-03 3:58 ` Andrew Morton
2007-04-03 4:45 ` Rusty Russell
2007-04-03 4:45 ` Rusty Russell
2007-04-03 4:57 ` Andrew Morton
2007-04-03 4:57 ` Andrew Morton
2007-04-03 5:44 ` [xfs-masters] " David Chinner
2007-04-03 5:44 ` David Chinner
2007-04-03 6:01 ` Andrew Morton
2007-04-03 6:01 ` Andrew Morton
2007-04-03 6:19 ` David Chinner
2007-04-03 6:19 ` David Chinner
2007-04-04 0:30 ` Rusty Russell
2007-04-04 0:30 ` Rusty Russell
2007-04-03 5:47 ` Rusty Russell
2007-04-03 5:47 ` Rusty Russell
2007-04-03 6:09 ` Andrew Morton
2007-04-03 6:09 ` Andrew Morton
2007-04-03 7:18 ` Rusty Russell
2007-04-03 7:18 ` Rusty Russell
2007-04-03 12:37 ` [xfs-masters] " David Chinner
2007-04-03 12:37 ` David Chinner
2007-04-03 17:36 ` Andrew Morton
2007-04-03 17:36 ` Andrew Morton
2007-04-04 0:03 ` David Chinner
2007-04-04 0:03 ` David Chinner
2007-04-03 9:57 ` Andi Kleen
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=20070402205825.12190e52.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=reiserfs-dev@namesys.com \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.