From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: DVD blockdevice buffers
Date: Fri, 25 May 2001 16:45:05 +0100 [thread overview]
Message-ID: <20010525164505.J7952@redhat.com> (raw)
In-Reply-To: <20010523205748.L8080@redhat.com> <Pine.LNX.4.31.0105231258420.6642-100000@penguin.transmeta.com> <20010524123627.L27177@redhat.com> <m1bsohh3da.fsf@frodo.biederman.org>
In-Reply-To: <m1bsohh3da.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Fri, May 25, 2001 at 09:09:37AM -0600
Hi,
On Fri, May 25, 2001 at 09:09:37AM -0600, Eric W. Biederman wrote:
> The case we don't get quite right are partial reads that hit cached
> data, on a page that doesn't have PG_Uptodate set. We don't actually
> need to do the I/O on the surrounding page to satisfy the read
> request. But we do because generic_file_read doesn't even think about
> that case.
That's *precisely* the case in question. The whole design of the page
cache involves reading entire pages at a time, in fact. We _could_
read in only partial pages, but in that case we end up wasting a lot
of the page.
> For the small random read case we could use a
> mapping->a_ops->readpartialpage
> function that sees if a request can be satisfied entirely
> from cached data. But this is just to allow generic_file_read
> to handle this, case.
Agreed. The only case where blockdev-in-pagecache really results in
significantly more IO is partial writes followed by partial reads.
Reads from totally-uncached pages ought to just fill the entire page
from disk; it's only when there is something already present
in the cache for that page that we want to look for partial buffers.
--Stephen
next prev parent reply other threads:[~2001-05-25 18:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 19:02 DVD blockdevice buffers Eduard Hasenleithner
2001-05-18 19:25 ` Jens Axboe
2001-05-18 19:59 ` Eduard Hasenleithner
2001-05-20 2:36 ` Linus Torvalds
2001-05-23 17:34 ` Stephen C. Tweedie
2001-05-23 18:12 ` Linus Torvalds
2001-05-23 19:57 ` Stephen C. Tweedie
2001-05-23 20:01 ` Linus Torvalds
2001-05-23 20:40 ` Jeff Garzik
2001-05-23 22:32 ` Andrea Arcangeli
2001-05-25 20:12 ` blkdev-pagecache-2 [was Re: DVD blockdevice buffers] Andrea Arcangeli
2001-05-25 20:15 ` Andrea Arcangeli
2001-05-23 22:09 ` DVD blockdevice buffers Andrea Arcangeli
2001-05-23 22:13 ` Alexander Viro
2001-05-23 22:24 ` Andrea Arcangeli
2001-05-24 11:36 ` Stephen C. Tweedie
2001-05-25 15:09 ` Eric W. Biederman
2001-05-25 15:45 ` Stephen C. Tweedie [this message]
2001-05-25 17:16 ` Linus Torvalds
2001-05-25 17:40 ` Alexander Viro
2001-05-25 18:05 ` Linus Torvalds
2001-05-25 18:24 ` Alexander Viro
2001-05-25 19:02 ` Stephen C. Tweedie
2001-05-27 6:38 ` Pavel Machek
2001-05-25 21:07 ` Eric W. Biederman
2001-05-25 21:18 ` Linus Torvalds
2001-05-25 22:31 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 18:16 Adam Schrotenboer
2001-05-19 22:56 ` Jens Axboe
2001-05-20 1:55 ` Adam Schrotenboer
2001-05-21 15:44 ` Adam Schrotenboer
2001-05-21 15:47 ` Jens Axboe
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=20010525164505.J7952@redhat.com \
--to=sct@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.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