public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: David Ashley <dash@xdr.com>, linux-kernel@vger.kernel.org
Subject: Re: Idea for improving linux buffer cache behaviour
Date: Sat, 4 Oct 2003 22:34:58 -0700	[thread overview]
Message-ID: <20031005053458.GC1205@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310041513150.14750-100000@chimarrao.boston.redhat.com>

On Sat, Oct 04, 2003 at 03:14:14PM -0400, Rik van Riel wrote:
> On Sat, 4 Oct 2003, David Ashley wrote:
> 
> > Forgive me if this has already been thought of, or is obsolete, or is
> > just plain a bad idea, but here it is:
> 
> Do you also want an answer if the kernel already does
> exactly what you are suggesting ? ;)
> 

Then why doesn't it work better?

> > 1) Lowest access count looked at first to toss
> > 2) If access counts equal, throw out oldest first
> 
> > The net result is commonly used items you very much want to remain in
> > cache always quickly get rated very highly as the system is used.
> 
> Which results in exactly the behaviour you're complaining
> about ;))

So, you use the system, have glibc loaded, and then play a dvd, and now
glibc needs to be re-read because it's not in cache.

Why wasn't glibc (one example) kept in cache with the streaming read from
the dvd?


  reply	other threads:[~2003-10-05  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04 15:34 Idea for improving linux buffer cache behaviour David Ashley
2003-10-04 19:14 ` Rik van Riel
2003-10-05  5:34   ` Mike Fedyk [this message]
2003-10-05 17:26     ` Helge Hafting
2003-10-05 17:56       ` CJ

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=20031005053458.GC1205@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=dash@xdr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@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