linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: PATCH: killing read_ahead[]
Date: Tue, 24 Oct 2000 18:16:31 -0600	[thread overview]
Message-ID: <20001024181631.B14069@vger.timpanogas.org> (raw)
In-Reply-To: <20001025003049.E18138@nightmaster.csn.tu-chemnitz.de>; from ingo.oeser@informatik.tu-chemnitz.de on Wed, Oct 25, 2000 at 12:30:49AM +0200

On Wed, Oct 25, 2000 at 12:30:49AM +0200, Ingo Oeser wrote:
> On Tue, Oct 24, 2000 at 12:46:36PM -0700, Linus Torvalds wrote:
> > Actually, the _real_ answer is to make fs/block_dev.c use the page cache
> > instead - and generic_file_read() does read-ahead that actually improves
> > performance, unlike the silly contortions that the direct block-dev
> > read-ahead tries to do.
> 
> If we had a paper about the page cache this would be easy.
> 
> In the beginning page cache was just previously mmaped pages,
> that are clean and ready to be mapped again.
> 
> Today we have them either dirty or clean, mapped or not(?), with and
> without buffers, in highmem(?) or lowmem and everybody and its
> children is using it for everything.
> 
> We need a clear definition about (concurrent) states of page
> cached pages, valid transitions (and locks/sema4s to take for
> them), assumptions, guarantees etc.
> 
> The only thing I see guaranteed, that every big thing to be
> cached should live there and is page aligned and page sized.
> 
> I'm trying hard to understand a concept in the page cache and to
> get it's limits and guarantees, but still find it hard to get
> them.
> 
> Time for specs, I would say ;-)
> 
> I could help to explain and formulate, if someone could only cut
> the edges of how it works and what it will be.
> 
> Thanks & Regards
> 
> Ingo Oeser
> -- 
> Feel the power of the penguin - run linux@your.pc
> <esc>:x
> -

I hope we are not doing something stupid here, like breaking the 
f*!%cking page cache again.  I've finaly got all the bugs out of 
NWFS on 2.4.0-test9, and have waded through the breakage of the 
past two testX releases of 2.4.   

Why do we need to disable read ahead on the page cache anyway?

:-)

Jeff



> 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/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

      reply	other threads:[~2000-10-25  0:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39F5DAF5.1D3662BD@mandrakesoft.com>
     [not found] ` <Pine.LNX.4.10.10010241245280.1704-100000@penguin.transmeta.com>
2000-10-24 22:30   ` Ingo Oeser
2000-10-25  0:16     ` Jeff V. Merkey [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=20001024181631.B14069@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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