public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dcache 2nd chance replacement
Date: Wed, 3 Jan 2001 22:12:21 +0100	[thread overview]
Message-ID: <20010103221221.I32185@athlon.random> (raw)
In-Reply-To: <20010103204354.E32185@athlon.random> <Pine.LNX.4.21.0101031745380.1403-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0101031745380.1403-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Wed, Jan 03, 2001 at 05:47:39PM -0200

On Wed, Jan 03, 2001 at 05:47:39PM -0200, Rik van Riel wrote:
> Not really. Under very high VFS loads we'd just scan
> through the list twice and free the entries anyway.

You're obviously wrong.

The higher was the load, the faster your working set was getting dropped from
the dcache. (with the patch the working set will have a chance to remains in
cache also with polluting going on instead, that's the whole point of aging:
to find out if something is worthwhile to keep in cache or not)

So the higher the VFS load definitely the higher improvement you will get.

The example with only pollution in the cache doesn't make sense, if you want to
optimize that case then remove the dcache in first place since it's only
overhead for such case.

Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-03 21:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 18:59 [PATCH] dcache 2nd chance replacement Rik van Riel
2001-01-03 19:05 ` Linus Torvalds
2001-01-03 19:11   ` Rik van Riel
2001-01-03 19:43 ` Andrea Arcangeli
2001-01-03 19:47   ` Rik van Riel
2001-01-03 21:12     ` Andrea Arcangeli [this message]
2001-01-03 23:09       ` Rik van Riel
2001-01-04  0:32         ` Andrea Arcangeli
2001-01-04 15:00           ` Rik van Riel
2001-01-04 16:18             ` Andrea Arcangeli
2001-01-04 16:23               ` Rik van Riel
2001-01-04 16:52                 ` Andrea Arcangeli
2001-01-04 16:59                   ` Rik van Riel
2001-01-04 17:35                     ` Andrea Arcangeli
2001-01-04 17:36                       ` Rik van Riel
2001-01-04 17:47                       ` Alan Cox
2001-01-05 12:08                         ` Chris Evans

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=20010103221221.I32185@athlon.random \
    --to=andrea@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=torvalds@transmeta.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