public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Helge Hafting <helgehaf@idb.hist.no>
Cc: Ivan Schreter <is@zapwerk.com>, linux-kernel@vger.kernel.org
Subject: Re: Buffer management - interesting idea
Date: 16 Jun 2001 11:35:25 -0700	[thread overview]
Message-ID: <992716525.22810.2.camel@ixodes.goop.org> (raw)
In-Reply-To: <3B29D048.4E19D545@idb.hist.no>
In-Reply-To: <01060613422800.07218@linux>  <3B29D048.4E19D545@idb.hist.no>

On 15 Jun 2001 11:07:20 +0200, Helge Hafting wrote:
> The "resistance to scanning" seemed interesting, maybe one-time
> activities like a "find" run or big cat/dd will have less impact with
> this.

It should also be good for streaming file use.  It gives a natural way
of detecting when you should be doing drop-behind (things fall out of
the fifo without ever making it into the LRU); doubly nice because it
works for both reads and writes without needing to treat them
differently.  It's also nice that it gives a natural interpretation to
the various madvise() flags.

    J


      parent reply	other threads:[~2001-06-16 18:36 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
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 [this message]

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=992716525.22810.2.camel@ixodes.goop.org \
    --to=jeremy@goop.org \
    --cc=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