From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, "Kasatkin,
Dmitry" <dmitry.kasatkin@intel.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: use WRITE_FLUSH instead of REQ_FLUSH
Date: Mon, 7 Jan 2013 09:23:49 -0500 [thread overview]
Message-ID: <20130107142348.GA5097@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1301070009230.7490@file.rdu.redhat.com>
On Mon, Jan 07 2013 at 12:12am -0500,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> Hi Alasdair
>
> Please push this patch to 3.8 kernel. (I already sent it before, but it
> was forgotten somehow).
>
> Mikulas
>
> ---
>
> dm-bufio: use WRITE_FLUSH instead of REQ_FLUSH
>
> Use WRITE_FLUSH instead of REQ_FLUSH to make it consistent with the rest
> of the kernel. There is no functional change - the kernel accepts either
> WRITE_FLUSH or REQ_FLUSH.
Well the important distinction is the flush bio is originating in
dm-bufio whereas other DM targets that test for REQ_FLUSH are just
passing the flush through. Saying as much makes the need for this patch
more explicit.
prev parent reply other threads:[~2013-01-07 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 5:12 [PATCH] use WRITE_FLUSH instead of REQ_FLUSH Mikulas Patocka
2013-01-07 14:23 ` 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=20130107142348.GA5097@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=mpatocka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.