From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Quinn Tran <quinn.tran@qlogic.com>,
sagi grimberg <sagig@mellanox.com>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Giridhar Malavali <giridhar.malavali@qlogic.com>,
Saurav Kashyap <saurav.kashyap@qlogic.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: Re: [PATCH 1/4] target/core: T10-Dif: check HW support capabilities
Date: Tue, 01 Apr 2014 13:09:37 -0400 [thread overview]
Message-ID: <yq1k3b9x9gu.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <533A71E9.90308@dev.mellanox.co.il> (Sagi Grimberg's message of "Tue, 01 Apr 2014 10:59:37 +0300")
>>>>> "Sagi" == Sagi Grimberg <sagig@dev.mellanox.co.il> writes:
Sagi> I originally wrote the code to support that. But it got left
Sagi> behind since I figured it is not an interesting use-case. If your
Sagi> beckend doesn't support T10-PI why should the target publish it
Sagi> support it and ask the device to strip/insert it? I suppose it is
Sagi> to allow the initiator to protect half-way, but I don't know how
Sagi> interesting it is if the data is not stored with protection...
That depends what you do on the backend. There are several devices out
there that expose PI to the host but use a different protection scheme
internally. And then synthesize PI on the host-facing side. Some even do
T10 PI to an internal protection scheme and then back to T10 PI when
talking to the disk drives in the back end.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-04-01 17:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 23:05 [PATCH RFC 0/4] add T10-Dif registration for tcm_qla2xxx Quinn Tran
2014-03-28 23:05 ` [PATCH 1/4] target/core: T10-Dif: check HW support capabilities Quinn Tran
2014-03-29 0:05 ` sagi grimberg
2014-03-29 0:53 ` Quinn Tran
2014-03-29 1:24 ` sagi grimberg
2014-03-31 17:53 ` Quinn Tran
2014-04-01 1:19 ` Nicholas A. Bellinger
2014-04-01 7:59 ` Sagi Grimberg
2014-04-01 17:09 ` Martin K. Petersen [this message]
2014-04-01 17:27 ` sagi grimberg
2014-04-01 17:45 ` Nicholas A. Bellinger
2014-04-02 6:51 ` Sagi Grimberg
2014-04-02 18:20 ` Nicholas A. Bellinger
2014-04-03 1:18 ` Quinn Tran
2014-04-02 11:43 ` sagi grimberg
2014-04-02 18:47 ` Nicholas A. Bellinger
2014-04-01 1:03 ` Nicholas A. Bellinger
2014-03-28 23:05 ` [PATCH 2/4] tcm_qla2xxx: T10-Dif set harware capability Quinn Tran
2014-03-29 0:12 ` sagi grimberg
2014-03-31 15:38 ` Quinn Tran
2014-04-01 1:11 ` Nicholas A. Bellinger
2014-04-01 8:04 ` Sagi Grimberg
2014-04-01 17:40 ` Nicholas A. Bellinger
2014-04-02 10:26 ` sagi grimberg
2014-03-28 23:05 ` [PATCH 3/4] target/rd: T10-Dif: Add init/format support Quinn Tran
2014-03-29 0:16 ` sagi grimberg
2014-03-31 16:14 ` Quinn Tran
2014-03-28 23:05 ` [PATCH 4/4] target/rd: T10-Dif: RAM disk is allocating more space than required Quinn Tran
2014-03-29 0:22 ` sagi grimberg
2014-03-31 16:15 ` Quinn Tran
2014-04-01 0:41 ` Nicholas A. Bellinger
2014-03-28 23:48 ` [PATCH RFC 0/4] add T10-Dif registration for tcm_qla2xxx Quinn Tran
2014-03-29 0:23 ` sagi grimberg
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=yq1k3b9x9gu.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=andrew.vasquez@qlogic.com \
--cc=giridhar.malavali@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=quinn.tran@qlogic.com \
--cc=sagig@dev.mellanox.co.il \
--cc=sagig@mellanox.com \
--cc=saurav.kashyap@qlogic.com \
--cc=target-devel@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 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.