From: Mike Snitzer <snitzer@redhat.com>
To: Jonathan Brassow <jbrassow@redhat.com>
Cc: dm-devel@redhat.com, linux-raid@vger.kernel.org, agk@redhat.com
Subject: Re: Add barrier support to dm-raid
Date: Tue, 28 Feb 2012 09:00:18 -0500 [thread overview]
Message-ID: <20120228140018.GB18849@redhat.com> (raw)
In-Reply-To: <1330437449.9910.2.camel@f14.redhat.com>
On Tue, Feb 28 2012 at 8:57am -0500,
Jonathan Brassow <jbrassow@redhat.com> wrote:
> Add barrier support to dm-raid.
>
> MD has support for barriers. DM core has support for barriers. Set the
> variable necessary to indicate to DM core that it is ok to pass down
> barrier requests - which dm-raid will simply pass along to MD.
>
> Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
Acked-by: Mike Snitzer <snitzer@redhat.com>
prev parent reply other threads:[~2012-02-28 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 13:57 [PATCH] Add barrier support to dm-raid Jonathan Brassow
2012-02-28 14:00 ` Mike Snitzer [this message]
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=20120228140018.GB18849@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jbrassow@redhat.com \
--cc=linux-raid@vger.kernel.org \
/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).