From: Linus Torvalds <torvalds@transmeta.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Ed Tomlinson <tomlins@cam.org>
Subject: Re: [PATCH][1/2] return values shrink_dcache_memory etc
Date: Sat, 20 Jul 2002 13:11:12 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0207201308180.1419-100000@home.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0207201639500.12241-100000@imladris.surriel.com>
On Sat, 20 Jul 2002, Rik van Riel wrote:
>
> this patch, against current 2.5.27, builds on the patch that let
> kmem_cache_shrink return the number of pages freed. This value
> is used as the return value for shrink_dcache_memory and friends.
I disagree with the whole approach of having shrink_cache() return the
number of pages free.
The number is meaningless, since it has nothing to do with the actual
memory zones that are under pressure (right now, the memory zone is almost
always ZONE_NORMAL, which is correct, but that's just pure luck rather
than anything fundamental).
I'd be much more interested in the "put the cache pages on the dirty list,
and have memory pressure push them out in LRU order" approach. Somebody
already had preliminary patches.
That gets _rid_ of dcache_shrink() and friends, instead of making them
return meaningless numbers.
Linus
--
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-07-20 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 19:40 Rik van Riel
2002-07-20 20:11 ` Linus Torvalds [this message]
2002-07-20 20:41 ` Rik van Riel
2002-07-20 20:53 ` Linus Torvalds
2002-07-20 21:42 ` Rik van Riel
2002-07-22 5:04 ` Andrew Morton
2002-07-22 5:16 ` William Lee Irwin III
2002-07-22 5:38 ` Andrew Morton
2002-07-22 6:06 ` Martin J. Bligh
2002-07-22 6:46 ` Andrew Morton
2002-07-22 7:20 ` Martin J. Bligh
2002-07-22 14:00 ` Rik van Riel
2002-07-22 13:34 ` Rik van Riel
2002-07-22 13:44 ` Rik van Riel
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.0207201308180.1419-100000@home.transmeta.com \
--to=torvalds@transmeta.com \
--cc=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