From: Helge Hafting <helgehaf@idb.hist.no>
To: Ivan Schreter <is@zapwerk.com>, linux-kernel@vger.kernel.org
Subject: Re: Buffer management - interesting idea
Date: Fri, 15 Jun 2001 11:07:20 +0200 [thread overview]
Message-ID: <3B29D048.4E19D545@idb.hist.no> (raw)
In-Reply-To: <01060613422800.07218@linux>
Ivan Schreter wrote:
>
> Hello,
>
> I'm working on some hi-speed DB projects under Linux and I was researching
> various buffer-replacement algorithms. I found 2Q buffer replacement policy at
>
> http://citeseer.nj.nec.com/63909.html
>
> Maybe it would be interesting to use it instead of LRU for disk buffer
> replacement. Seems relatively easy to implement and costs are about the same as
> for LRU.
The "resistance to scanning" seemed interesting, maybe one-time
activities like a "find" run or big cat/dd will have less impact with
this.
Helge Hafting
next prev parent reply other threads:[~2001-06-15 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 11:39 Buffer management - interesting idea Ivan Schreter
2001-06-15 9:07 ` Helge Hafting [this message]
2001-06-15 9:41 ` Ivan Schreter
[not found] ` <Pine.LNX.4.33.0106151219430.9557-100000@pianoman.cluster.toy>
2001-06-15 17:05 ` Ivan Schreter
2001-06-15 18:50 ` Rik van Riel
2001-06-15 23:51 ` Ivan Schreter
2001-06-16 18:35 ` Jeremy Fitzhardinge
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=3B29D048.4E19D545@idb.hist.no \
--to=helgehaf@idb.hist.no \
--cc=is@zapwerk.com \
--cc=linux-kernel@vger.kernel.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