From: Nikanth Karthikesan <knikanth@suse.de>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: [PATCH] dm_crypt: Issue all previous bios before remapping barrier bio
Date: Wed, 3 Feb 2010 11:39:15 +0530 [thread overview]
Message-ID: <201002031139.15659.knikanth@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1002020743340.30625@hs20-bc2-1.build.redhat.com>
On Tuesday 02 February 2010 18:17:24 Mikulas Patocka wrote:
> On Mon, 1 Feb 2010, Milan Broz wrote:
> > On 02/01/2010 04:19 PM, Nikanth Karthikesan wrote:
> > > Before remapping a barrier bio, make sure that there are no un-issued
> > > pending I/O in the workqueue. Otherwise a dm_flush would simply add
> > > a barrier request to the underlying device, without issuing the bio's
> > > queued in the dm_crypt device.
> >
> > This should not be needed. Core dm code waits for all bios submitted
> > before barrier requests.
> >
> > Mikulas, could you verify it?
> >
> > Milan
>
> Yes, you are right, the patch is not needed.
>
> When the target receives an empty barrier request, there are no other data
> requests in flight.
>
> BTW. The target may receive more empty barrier requests simultaneously, if
> it asked for it by setting ti->num_flush_requests to more than one. But
> barrier and non-barrier requests are never mixed.
>
Correct. Sorry, I was a bit hasty in sending that patch. It is not required.
Thanks for the patient explanation.
Thanks
Nikanth
prev parent reply other threads:[~2010-02-03 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 15:19 [PATCH] dm_crypt: Issue all previous bios before remapping barrier bio Nikanth Karthikesan
2010-02-01 15:39 ` Milan Broz
2010-02-02 12:47 ` Mikulas Patocka
2010-02-03 6:09 ` Nikanth Karthikesan [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=201002031139.15659.knikanth@suse.de \
--to=knikanth@suse.de \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.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.