From: Alasdair G Kergon <agk@redhat.com>
To: Ric Wheeler <ric@emc.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
device-mapper development <dm-devel@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] Re: [PATCH] Implement barrier support for single device DM devices
Date: Tue, 19 Feb 2008 02:45:33 +0000 [thread overview]
Message-ID: <20080219024533.GC4066@agk.fab.redhat.com> (raw)
In-Reply-To: <47B98D8A.7090506@emc.com>
On Mon, Feb 18, 2008 at 08:52:10AM -0500, Ric Wheeler wrote:
> I understand that. Most of the time, dm or md devices are composed of
> uniform components which will uniformly support (or not) the cache flush
> commands used by barriers.
As a dm developer, it's "almost none of the time" because trivial
configurations aren't the ones that require lots of testing effort.
Let's stop arguing over "most of the time":-)
As Andi points out, there are certainly enough real-world users of
"single linear or crypt target using one physical device" for it to be
worth our supporting it.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2008-02-19 2:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 12:08 Andi Kleen
2008-02-15 12:20 ` Alasdair G Kergon
2008-02-15 13:07 ` Michael Tokarev
2008-02-15 14:20 ` Andi Kleen
2008-02-15 14:12 ` [dm-devel] " Alasdair G Kergon
2008-02-15 15:34 ` Andi Kleen
2008-02-15 15:31 ` Alan Cox
2008-02-18 12:48 ` Ric Wheeler
2008-02-18 13:24 ` Michael Tokarev
2008-02-18 13:52 ` Ric Wheeler
2008-02-19 2:45 ` Alasdair G Kergon [this message]
2008-05-16 19:55 ` Mike Snitzer
2008-05-16 21:48 ` Andi Kleen
2008-02-18 22:16 ` David Chinner
2008-02-19 2:56 ` Alasdair G Kergon
2008-02-19 5:36 ` David Chinner
2008-02-19 9:43 ` Andi Kleen
2008-02-19 7:19 ` Jeremy Higdon
2008-02-19 7:58 ` Michael Tokarev
2008-02-20 13:38 ` Ric Wheeler
2008-02-21 3:29 ` Neil Brown
2008-02-21 3:39 ` Neil Brown
2008-02-17 23:31 ` David Chinner
2008-02-19 2:39 ` Alasdair G Kergon
2008-02-19 11:12 ` David Chinner
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=20080219024533.GC4066@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=andi@firstfloor.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=ric@emc.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
Powered by JetHome