From: Linus Torvalds <torvalds@transmeta.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Benjamin Redelings I <bredelin@ucsd.edu>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: [2.1.130-3] Page cache DEFINATELY too persistant... feature?
Date: Fri, 27 Nov 1998 10:31:04 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.3.95.981127103023.21897G-100000@penguin.transmeta.com> (raw)
In-Reply-To: <199811271602.QAA00642@dax.scot.redhat.com>
On Fri, 27 Nov 1998, Stephen C. Tweedie wrote:
>
> The patch below both makes sense from this perspective and seems to
> work, which is always a good sign! Moreover, it is inherently
> self-tuning. The more recently-accessed cache pages we encounter, the
> faster we will age the cache.
Looks sane to me. The previous counters never had any good reason behind
them either, this at least tries to reason about it. Applied.
Linus
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-11-26 23:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199811261236.MAA14785@dax.scot.redhat.com>
[not found] ` <Pine.LNX.3.95.981126094159.5186D-100000@penguin.transmeta.com>
1998-11-27 16:02 ` Stephen C. Tweedie
1998-11-27 17:19 ` Chip Salzenberg
1998-11-27 18:31 ` Linus Torvalds [this message]
1998-11-27 19:58 ` Zlatko Calusic
1998-11-30 11:15 ` Stephen C. Tweedie
1998-11-30 23:13 ` Zlatko Calusic
1998-11-30 12:37 ` Rik van Riel
1998-11-30 15:12 ` Zlatko Calusic
1998-11-30 19:29 ` Rik van Riel
1998-11-30 22:27 ` Zlatko Calusic
1998-11-30 23:11 ` Rik van Riel
1998-11-30 20:20 ` Andrea Arcangeli
1998-11-30 22:28 ` Zlatko Calusic
1998-11-28 7:31 ` Eric W. Biederman
1998-11-30 11:13 ` Stephen C. Tweedie
1998-11-30 15:08 ` Rik van Riel
1998-11-30 21:40 ` Eric W. Biederman
1998-11-30 22:00 ` Eric W. Biederman
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.3.95.981127103023.21897G-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=bredelin@ucsd.edu \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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