From: "Stephen C. Tweedie" <sct@redhat.com>
To: Daniel Phillips <phillips@innominate.de>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: inode->i_dirty_buffers redundant ?
Date: Fri, 26 Jan 2001 11:35:07 +0000 [thread overview]
Message-ID: <20010126113507.J11607@redhat.com> (raw)
In-Reply-To: <200101251047.QAA16434@vxindia.veritas.com> <20010125164432.A12984@redhat.com> <3A708722.C21EC12A@innominate.de>
In-Reply-To: <3A708722.C21EC12A@innominate.de>; from phillips@innominate.de on Thu, Jan 25, 2001 at 09:05:54PM +0100
Hi,
On Thu, Jan 25, 2001 at 09:05:54PM +0100, Daniel Phillips wrote:
> "Stephen C. Tweedie" wrote:
> > We also maintain the
> > per-page buffer lists as caches of the virtual-to-physical mapping to
> > avoid redundant bmap()ping.
>
> Could you clarify that one, please?
The buffer contains a physical label for the block's location on disk.
The page cache is indexed purely by logical location, so doing IO
to/from the page cache requires us to lookup the physical locations of
each block within the page.
Caching the buffer_heads for page cache pages means that once those
lookups are done once, further IO on the same page can bypass the
lookup and go straight to disk.
--Stephen
-
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/
next prev parent reply other threads:[~2001-01-26 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 10:47 inode->i_dirty_buffers redundant ? V Ganesh
2001-01-25 16:44 ` Stephen C. Tweedie
2001-01-25 20:05 ` Daniel Phillips
2001-01-25 21:30 ` Marcelo Tosatti
2001-01-26 11:35 ` Stephen C. Tweedie [this message]
2001-01-26 19:05 ` Daniel Phillips
2001-01-25 21:11 ` Marcelo Tosatti
2001-01-26 17:34 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 9:13 V Ganesh
2001-01-24 9:55 V Ganesh
2001-01-24 9:09 ` Marcelo Tosatti
2001-01-24 11:26 ` Stephen C. Tweedie
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=20010126113507.J11607@redhat.com \
--to=sct@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@innominate.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.