From: Neil Brown <neilb@suse.de>
To: djwong@us.ibm.com
Cc: linux-raid@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] md: Call blk_queue_flush() to establish flush/fua support
Date: Wed, 24 Nov 2010 16:18:13 +1100 [thread overview]
Message-ID: <20101124161813.2f5bc0d6@notabene.brown> (raw)
In-Reply-To: <20101123190103.GW14383@tux1.beaverton.ibm.com>
On Tue, 23 Nov 2010 11:01:03 -0800
"Darrick J. Wong" <djwong@us.ibm.com> wrote:
> Here's a shorter version that sets up flush/fua unconditionally.
> ---
> Before 2.6.37, the md layer had a mechanism for catching I/Os with the barrier
> flag set, and translating the barrier into barriers for all the underlying
> devices. With 2.6.37, I/O barriers have become plain old flushes, and the md
> code was updated to reflect this. However, one piece was left out -- the md
> layer does not tell the block layer that it supports flushes or FUA access at
> all, which results in md silently dropping flush requests.
>
> Since the support already seems there, just add this one piece of bookkeeping.
>
> Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
> ---
>
> drivers/md/md.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 324a366..43243a4 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -4338,6 +4338,8 @@ static int md_alloc(dev_t dev, char *name)
> if (mddev->kobj.sd &&
> sysfs_create_group(&mddev->kobj, &md_bitmap_group))
> printk(KERN_DEBUG "pointless warning\n");
> +
> + blk_queue_flush(mddev->queue, REQ_FLUSH | REQ_FUA);
> abort:
> mutex_unlock(&disks_mutex);
> if (!error && mddev->kobj.sd) {
Applied, thanks.
NeilBrown
prev parent reply other threads:[~2010-11-24 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 23:22 [PATCH] md: Call blk_queue_flush() to establish flush/fua support Darrick J. Wong
2010-11-22 23:50 ` Neil Brown
2010-11-23 1:28 ` Darrick J. Wong
2010-11-23 19:01 ` [PATCH v2] " Darrick J. Wong
2010-11-24 5:18 ` Neil Brown [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=20101124161813.2f5bc0d6@notabene.brown \
--to=neilb@suse.de \
--cc=djwong@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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).