From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: "Nicholas A. Bellinger" <nab@daterainc.com>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
Sagi Grimberg <sagig@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Roland Dreier <roland@kernel.org>
Subject: Re: [PATCH-v2 11/17] target/iblock: Add blk_integrity + BIP passthrough support
Date: Tue, 21 Jan 2014 14:20:17 -0800 [thread overview]
Message-ID: <1390342817.5567.778.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <52DBC32C.4060505@dev.mellanox.co.il>
On Sun, 2014-01-19 at 14:21 +0200, Sagi Grimberg wrote:
> On 1/19/2014 4:44 AM, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger <nab@linux-iscsi.org>
> >
> > This patch adds blk_integrity passthrough support for block_device
> > backends using IBLOCK.
>
> Nice!
>
> > This includes iblock_alloc_bip() + setup of bio_integrity_payload
> > information that attaches to the leading struct bio once bio_list
> > is populated during fast-path iblock_execute_rw() I/O dispatch.
> >
> > It also updates setup in iblock_configure_device() to detect modes
> > of protection + se dev->dev_attrib.pi_prot_type accordingly, along
> > with creating required bio_set integrity mempools.
> >
> > Cc: Martin K. Petersen <martin.petersen@oracle.com>
> > Cc: Christoph Hellwig <hch@lst.de>
> > Cc: Hannes Reinecke <hare@suse.de>
> > Cc: Sagi Grimberg <sagig@mellanox.com>
> > Cc: Or Gerlitz <ogerlitz@mellanox.com>
> > Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
> > ---
> > drivers/target/Kconfig | 1 +
> > drivers/target/target_core_iblock.c | 91 ++++++++++++++++++++++++++++++++++-
> > 2 files changed, 90 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/target/Kconfig b/drivers/target/Kconfig
> > index 50aad2e..dc2d84a 100644
> > --- a/drivers/target/Kconfig
> > +++ b/drivers/target/Kconfig
> > @@ -14,6 +14,7 @@ if TARGET_CORE
> >
> > config TCM_IBLOCK
> > tristate "TCM/IBLOCK Subsystem Plugin for Linux/BLOCK"
> > + select BLK_DEV_INTEGRITY
> > help
> > Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
> > access to Linux/Block devices using BIO
> > diff --git a/drivers/target/target_core_iblock.c b/drivers/target/target_core_iblock.c
> > index 15d9121..293d9b0 100644
> > --- a/drivers/target/target_core_iblock.c
> > +++ b/drivers/target/target_core_iblock.c
> > @@ -91,6 +91,7 @@ static int iblock_configure_device(struct se_device *dev)
> > struct iblock_dev *ib_dev = IBLOCK_DEV(dev);
> > struct request_queue *q;
> > struct block_device *bd = NULL;
> > + struct blk_integrity *bi;
> > fmode_t mode;
> > int ret = -ENOMEM;
> >
> > @@ -155,8 +156,40 @@ static int iblock_configure_device(struct se_device *dev)
> > if (blk_queue_nonrot(q))
> > dev->dev_attrib.is_nonrot = 1;
> >
> > + bi = bdev_get_integrity(bd);
> > + if (bi) {
> > + struct bio_set *bs = ib_dev->ibd_bio_set;
> > +
> > + if (!strcmp(bi->name, "T10-DIF-TYPE3-IP") ||
> > + !strcmp(bi->name, "T10-DIF-TYPE1-IP")) {
> > + pr_err("IBLOCK export of blk_integrity: %s not"
> > + " supported\n", bi->name);
> > + ret = -ENOSYS;
> > + goto out_blkdev_put;
> > + }
>
> Please remind me why we ignore IP-CSUM guard type again?
> MKP, will this be irrelevant for the initiator as well? if so, I don't
> see a reason to expose this in RDMA verbs.
My understanding is that this was used for pre-production prototyping,
and is not supported by any real backend storage hardware.
--nab
next prev parent reply other threads:[~2014-01-21 22:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 2:44 [PATCH-v2 00/17] target: Add support for DIF Type1+Type3 emulation + passthrough Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 01/17] target: Add DIF related base definitions Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 02/17] target: Add DIF CHECK_CONDITION ASC/ASCQ exception cases Nicholas A. Bellinger
2014-01-22 16:44 ` Sagi Grimberg
2014-01-22 22:16 ` Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 03/17] target/sbc: Add DIF setup in sbc_check_prot + sbc_parse_cdb Nicholas A. Bellinger
2014-01-19 11:43 ` Sagi Grimberg
2014-01-21 22:48 ` Nicholas A. Bellinger
2014-01-22 18:00 ` Sagi Grimberg
2014-01-22 22:27 ` Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 04/17] target/sbc: Add DIF TYPE1+TYPE3 read/write verify emulation Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 05/17] target/spc: Add protection bit to standard INQUIRY output Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 06/17] target/spc: Add protection related bits to INQUIRY EVPD=0x86 Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 07/17] target/sbc: Add P_TYPE + PROT_EN bits to READ_CAPACITY_16 Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 08/17] target/spc: Expose ATO bit in control mode page Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 09/17] target/configfs: Expose protection device attributes Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 10/17] target: Add protection SGLs to target_submit_cmd_map_sgls Nicholas A. Bellinger
2014-01-19 12:12 ` Sagi Grimberg
2014-01-21 22:17 ` Nicholas A. Bellinger
2014-01-22 10:07 ` Sagi Grimberg
2014-01-19 2:44 ` [PATCH-v2 11/17] target/iblock: Add blk_integrity + BIP passthrough support Nicholas A. Bellinger
2014-01-19 12:21 ` Sagi Grimberg
2014-01-21 22:20 ` Nicholas A. Bellinger [this message]
2014-01-22 1:54 ` Martin K. Petersen
2014-01-22 1:52 ` Martin K. Petersen
2014-01-22 10:09 ` Sagi Grimberg
2014-01-19 2:44 ` [PATCH-v2 12/17] target/file: Add DIF protection init/format support Nicholas A. Bellinger
2014-01-19 12:31 ` Sagi Grimberg
2014-01-21 22:28 ` Nicholas A. Bellinger
2014-01-22 10:12 ` Sagi Grimberg
2014-01-22 22:13 ` Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 13/17] target/file: Add DIF protection support to fd_execute_rw Nicholas A. Bellinger
2014-01-19 12:37 ` Sagi Grimberg
2014-01-19 2:44 ` [PATCH-v2 14/17] target/rd: Refactor rd_build_device_space + rd_release_device_space Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 15/17] target/rd: Add support for protection SGL setup + release Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 16/17] target/rd: Add DIF protection into rd_execute_rw Nicholas A. Bellinger
2014-01-19 2:44 ` [PATCH-v2 17/17] tcm_loop: Enable DIF/DIX modes in SCSI host LLD Nicholas A. Bellinger
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=1390342817.5567.778.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nab@daterainc.com \
--cc=ogerlitz@mellanox.com \
--cc=roland@kernel.org \
--cc=sagig@dev.mellanox.co.il \
--cc=sagig@mellanox.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 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®