From: Yibin Wang <wangyibin@huawei.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jiangyiwen <jiangyiwen@huawei.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: dm-mpath: Handling SCSI-3 PR RELEASE in multi-controller environment
Date: Thu, 13 Oct 2016 19:16:13 +0800 [thread overview]
Message-ID: <57FF6CFD.3060708@huawei.com> (raw)
In-Reply-To: <57FF5194.4030402@huawei.com>
On 2016/10/13 17:19, Yibin Wang wrote:
> Hi Christoph,
>
> Thanks for your reply. Comments inline...
>
> On 2016/10/9 23:16, Christoph Hellwig wrote:
> ......
>>
>>> - For regisetr, we should stop iteration on failure, and
>>> followed by a
>>> non-stopping unregister operation.
>> What do you mean with "non-stopping"? Currently once register failed
>> for a path we then ungerigster all paths, and ignore failures (e.g. due
>> to a down path or an not already registered path).
>
BTW, did you mean using dm_pr::fail_early as the indication whether
multipath_iterate_devices() should fail early upon failure? If that's
the case,
I can't see it is used anywhere except in dm_pr_register().
Please correct me if I am wrong. Thanks!
> That's exactly what I meant - do not stop on failures while doing
> unregistration.
next prev parent reply other threads:[~2016-10-13 11:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 13:12 dm-mpath: Handling SCSI-3 PR RELEASE in multi-controller environment wangyibin
2016-10-09 15:16 ` Christoph Hellwig
2016-10-13 9:19 ` Yibin Wang
2016-10-13 11:16 ` Yibin Wang [this message]
2016-10-14 13:48 ` Christoph Hellwig
2016-10-14 14:51 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2016-09-21 9:14 jiangyiwen
2016-09-21 15:04 ` Mike Snitzer
2016-09-21 17:14 ` Christoph Hellwig
2016-09-22 8:14 ` jiangyiwen
2016-09-26 16:03 ` Christoph Hellwig
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=57FF6CFD.3060708@huawei.com \
--to=wangyibin@huawei.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jiangyiwen@huawei.com \
--cc=snitzer@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.