From: Arnd Bergmann <arnd@arndb.de>
To: "Jörn Engel" <joern@logfs.org>
Cc: Dongjun Shin <djshin90@gmail.com>, Greg Banks <gnb@sgi.com>,
Linux Filesystem Mailing List <linux-fsdevel@vger.kernel.org>,
David Chinner <dgc@melbourne.sgi.com>,
Donald Douwsma <donaldd@melbourne.sgi.com>,
Christoph Hellwig <hch@infradead.org>,
Roger Strassburg <rls@sgi.com>, Mark Goodwin <markgw@sgi.com>,
Brett Jon Grandbois <brettg@melbourne.sgi.com>
Subject: Re: Proposal to improve filesystem/block snapshot interaction
Date: Tue, 30 Oct 2007 17:37:27 +0100 [thread overview]
Message-ID: <200710301737.29007.arnd@arndb.de> (raw)
In-Reply-To: <20071030153707.GC13455@lazybastard.org>
On Tuesday 30 October 2007, Jörn Engel wrote:
> On Tue, 30 October 2007 23:19:48 +0900, Dongjun Shin wrote:
> > On 10/30/07, Arnd Bergmann <arnd@arndb.de> wrote:
> > >
> > > Not sure. Why shouldn't you be able to reorder the hints provided that
> > > they don't overlap with read/write bios for the same block?
> >
> > You're right. The bios can be reordered if they don't overlap with hint.
>
> I would keep things simpler. Bios can be reordered, full stop. If an
> erase and a write overlap, the caller (filesystem?) has to add a
> barrier.
I thought bios were already ordered if they affect the same blocks.
Either way, I agree that an erase should not be treated special on
the bio layer, its ordering should be handled the same way we do it
for writes.
Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-10-30 16:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070927063113.GD2989@sgi.com>
2007-10-30 1:04 ` Proposal to improve filesystem/block snapshot interaction Greg Banks
2007-10-30 1:11 ` Greg Banks
2007-10-30 4:16 ` Neil Brown
2007-10-30 5:12 ` Greg Banks
2007-10-30 7:43 ` Arnd Bergmann
2007-11-20 23:43 ` Roger Strassburg
2007-10-30 23:56 ` David Chinner
2007-10-31 4:01 ` Greg Banks
2007-10-31 7:04 ` David Chinner
2007-10-30 9:35 ` Dongjun Shin
2007-10-30 10:15 ` Arnd Bergmann
2007-10-30 10:49 ` Dongjun Shin
2007-10-30 12:38 ` Arnd Bergmann
2007-10-30 14:19 ` Dongjun Shin
2007-10-30 15:37 ` Jörn Engel
2007-10-30 16:37 ` Arnd Bergmann [this message]
2007-10-30 23:19 ` Kyungmin Park
2007-10-30 23:42 ` Kyungmin Park
2007-10-30 14:06 ` Jörn Engel
2007-10-31 3:44 ` Greg Banks
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=200710301737.29007.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=brettg@melbourne.sgi.com \
--cc=dgc@melbourne.sgi.com \
--cc=djshin90@gmail.com \
--cc=donaldd@melbourne.sgi.com \
--cc=gnb@sgi.com \
--cc=hch@infradead.org \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=markgw@sgi.com \
--cc=rls@sgi.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;
as well as URLs for NNTP newsgroup(s).