From: Bodo Eggert <7eggert@gmx.de>
To: Eric Sandeen <sandeen@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>,
Andi Kleen <andi@firstfloor.org>,
?missing.closing.'"' in token?"MASON",
CHRISTOPHER <CHRIS.MASON@oracle.com>"@vax.1wt.eu
Subject: Re: Barriers still not passing on simple dm devices...
Date: Mon, 23 Mar 2009 22:52:31 +0100 [thread overview]
Message-ID: <E1Lls4N-0001LL-Pz@be1.7eggert.dyndns.org> (raw)
In-Reply-To: <ciXHh-39c-37@gated-at.bofh.it>
Eric Sandeen <sandeen@redhat.com> wrote:
> I've noticed that on 2.6.29-rcX, with Andi's patch
> (ab4c1424882be9cd70b89abf2b484add355712fa, dm: support barriers on
> simple devices) barriers are still getting rejected on these simple devices.
> So what's the right way around this? What should dm (or md for that
> matter) advertise on their queues about ordered-ness? Should there be
> some sort of "QUEUE_ORDERED_PASSTHROUGH" or something to say "this level
> doesn't care, ask the next level" or somesuch? Or should it inherit the
> flag from the next level down? Ideas?
IMO each block device SHOULD provide barriers - either native or emulated,
and each meta device MUST provide emulated barriers if it provides dynamic
device binding and barriers.
next parent reply other threads:[~2009-03-23 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ciXHh-39c-37@gated-at.bofh.it>
2009-03-23 21:52 ` Bodo Eggert [this message]
[not found] ` <cjfuL-6vJ-43@gated-at.bofh.it>
[not found] ` <cjfEl-6J2-45@gated-at.bofh.it>
[not found] ` <cjfNX-6Wh-27@gated-at.bofh.it>
2009-03-26 13:05 ` [dm-devel] " Bodo Eggert
[not found] ` <cjfXx-78D-9@gated-at.bofh.it>
[not found] ` <cjg7h-7lM-29@gated-at.bofh.it>
[not found] ` <cjgqC-80G-21@gated-at.bofh.it>
[not found] ` <cjD3I-22U-7@gated-at.bofh.it>
[not found] ` <cjDdE-2g3-31@gated-at.bofh.it>
[not found] ` <cjJVv-4vp-13@gated-at.bofh.it>
[not found] ` <cjXlS-uM-1@gated-at.bofh.it>
2009-03-26 15:26 ` Bodo Eggert
2009-03-23 19:04 Eric Sandeen
2009-03-23 19:10 ` Eric Sandeen
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=E1Lls4N-0001LL-Pz@be1.7eggert.dyndns.org \
--to=7eggert@gmx.de \
--cc=andi@firstfloor.org \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@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
all inboxes | Powered by JetHome®