From: John Garry <john.garry@huawei.com>
To: <jejb@linux.vnet.ibm.com>, <martin.petersen@oracle.com>
Cc: <linuxarm@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-scsi@vger.kernel.org>, John Garry <john.garry@huawei.com>
Subject: [PATCH v5 0/2] hisi_sas: DIF support
Date: Mon, 17 Dec 2018 22:40:06 +0800 [thread overview]
Message-ID: <1545057608-89965-1-git-send-email-john.garry@huawei.com> (raw)
This patchset introduces support to the driver for DIF/DIX.
We are making DIX support as RFC for now, based on issues discussed in the
following:
https://marc.info/?l=linux-scsi&m=154357719329297&w=4 and
https://marc.info/?l=linux-scsi&m=154406987703456&w=2
We will only support PI in v3 hw at the moment, even though previous hw
versions also support it.
Differences:
v4->v5:
- Drop already accepted patches
- Fix comments according to Martin
- use t10_pi_ref_tag()
- stop using protection options in LLDD in favour of prot flags
- allow user to set prot mask
v3->v4:
- re-add DIX support as RFC - do not commit please!
- also DIX support is labelled experimental in the driver
v2->v3:
- fix sparse warnings
- drop DIX support
v1->v2:
- drop scsi_prot_op_normal()
Xiang Chen (2):
scsi: hisi_sas: Add support for DIF feature for v2 hw
scsi: hisi_sas: Add support for DIX feature for v3 hw as experimental
drivers/scsi/hisi_sas/hisi_sas.h | 28 +++++
drivers/scsi/hisi_sas/hisi_sas_main.c | 97 ++++++++++++++--
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 197 ++++++++++++++++++++++++++++++++-
3 files changed, 305 insertions(+), 17 deletions(-)
--
1.9.1
next reply other threads:[~2018-12-17 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 14:40 John Garry [this message]
2018-12-17 14:40 ` [PATCH v5 1/2] scsi: hisi_sas: Add support for DIF feature for v2 hw John Garry
2018-12-19 4:35 ` Martin K. Petersen
2018-12-19 15:02 ` John Garry
2018-12-17 14:40 ` [RFC PATCH v5 2/2] scsi: hisi_sas: Add support for DIX feature for v3 hw as experimental John Garry
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=1545057608-89965-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®