public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Christopher S. Swingley" <cswingle@iarc.uaf.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.13-ac1
Date: Fri, 26 Oct 2001 19:43:01 +0200	[thread overview]
Message-ID: <20011026194301.M30905@athlon.random> (raw)
In-Reply-To: <20011026092359.A9384@iarc.uaf.edu> <E15xAso-0000mW-00@the-village.bc.nu>
In-Reply-To: <E15xAso-0000mW-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Oct 26, 2001 at 06:35:02PM +0100

On Fri, Oct 26, 2001 at 06:35:02PM +0100, Alan Cox wrote:
> > Does this mean the ac tree now uses the AA VM, or is this a merge
> > with everything but the VM, like the earlier 2.4.1x-ac trees?
> 
> It still uses buffer cache based raw disk access (so things like DVD players

btw, AFIK the fact dvd player can hang some millisecond across a
close/open cycle, isn't really because of the blkdev in pagecache but
simply because the <2.4.10 buffer cache layer wasn't able to do proper
readahead on the blkdev. Now we do readahead properly and so in turn
the the lack of media-change trust of the vfs shows up. So as far I can
tell the right fix have no influence on the blkdev in pagecache, but it
only consists in resurrecting the media-change detection with a
per-device bitflag whitelist. I cannot see other source of stalls across
a close/open cycle.

Andrea

  reply	other threads:[~2001-10-26 17:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.kgfmokv.12jgvrv@ifi.uio.no>
2001-10-26 16:04 ` Linux 2.4.13-ac1 John Weber
2001-10-26 17:23   ` Christopher S. Swingley
2001-10-26 17:35     ` Alan Cox
2001-10-26 17:43       ` Andrea Arcangeli [this message]
2001-10-26 17:54         ` Alan Cox
2001-10-26 18:00           ` Andrea Arcangeli
2001-10-26 14:50 Alan Cox

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=20011026194301.M30905@athlon.random \
    --to=andrea@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cswingle@iarc.uaf.edu \
    --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