From: Christoph Hellwig <hch@caldera.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Rajagopal Ananthanarayanan <ananth@sgi.com>,
Rik van Riel <riel@conectiva.com.br>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] generic IO write clustering
Date: Sat, 20 Jan 2001 20:05:15 +0100 [thread overview]
Message-ID: <20010120200514.A26170@caldera.de> (raw)
In-Reply-To: <20010120184506.A21943@caldera.de> <Pine.LNX.4.21.0101201358340.6593-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0101201358340.6593-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Sat, Jan 20, 2001 at 02:00:24PM -0200
On Sat, Jan 20, 2001 at 02:00:24PM -0200, Marcelo Tosatti wrote:
> > True. But you have to go through ext2_get_branch (under the big kernel
> > lock) - if we can do only one logical->physical block translations,
> > why doing it multiple times?
>
> You dont. If the metadata is cached and uptodate there is no need to call
> get_block().
Ups. You are right for the stock tree - I was only looking at my kio tree,
where it can't be cached due to the lack of buffer-cache usage...
Christoph
--
Whip me. Beat me. Make me maintain AIX.
-
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-20 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 0:34 [RFC] generic IO write clustering Marcelo Tosatti
2001-01-20 2:58 ` Rik van Riel
2001-01-20 1:52 ` Marcelo Tosatti
2001-01-20 15:57 ` Christoph Hellwig
2001-01-20 15:24 ` Marcelo Tosatti
2001-01-20 17:45 ` Christoph Hellwig
2001-01-20 16:00 ` Marcelo Tosatti
2001-01-20 19:05 ` Christoph Hellwig [this message]
2001-01-20 17:55 ` Marcelo Tosatti
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=20010120200514.A26170@caldera.de \
--to=hch@caldera.de \
--cc=ananth@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
--cc=sct@redhat.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