From: Christoph Hellwig <hch@infradead.org>
To: Guan Junxiong <guanjunxiong@huawei.com>
Cc: Christoph Hellwig <hch@infradead.org>,
agk@redhat.com, snitzer@redhat.com,
"Hege (A)" <hege09@huawei.com>,
shenhong09@huawei.com, Yang Feng <philip.yang@huawei.com>,
"Zouming (IT)" <zouming.zouming@huawei.com>,
dm-devel@redhat.com, linux-scsi@vger.kernel.org
Subject: Re: [Consult]: Can the coming Huawei scsi device handler be accepted in the scsi/device_handler
Date: Sun, 14 May 2017 22:34:18 -0700 [thread overview]
Message-ID: <20170515053418.GA17024@infradead.org> (raw)
In-Reply-To: <70bd5fb5-a612-53d3-cc39-92ade30de9c0@huawei.com>
On Mon, May 15, 2017 at 12:08:12PM +0800, Guan Junxiong wrote:
> Hi, Christoph Hellwig
> Thanks for your reply. But I am a little confused:
>
> Our Huawei scsi device handler will support ALUA. Besides , some new enhancements such as error self negotiation
> on the scsi (maybe NMVe in the future) error status handling to enhance reliability. Here are two choices:
> 1) Alter the scsi_dh_alua.c directly and make a generic way to handle error status.
> 2) Add a new file named scsi_dh_huawei.c which implements the ALUA feature and error negotiation feature.
>
> Can those two choices be accepted by linux-scsi?
The choice is
(3) get your enhancements standardized in T10 and NVMe.
prev parent reply other threads:[~2017-05-15 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a708085e-e9f0-3b5f-0290-00db8071a6b2@huawei.com>
2017-05-13 7:37 ` [dm-devel] [Consult]: Can the coming Huawei scsi device handler be accepted in the scsi/device_handler Christoph Hellwig
2017-05-15 4:08 ` Guan Junxiong
2017-05-15 5:34 ` Christoph Hellwig [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=20170515053418.GA17024@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=guanjunxiong@huawei.com \
--cc=hege09@huawei.com \
--cc=linux-scsi@vger.kernel.org \
--cc=philip.yang@huawei.com \
--cc=shenhong09@huawei.com \
--cc=snitzer@redhat.com \
--cc=zouming.zouming@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox