mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
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 12/17] target/file: Add DIF protection init/format support
Date: Wed, 22 Jan 2014 12:12:25 +0200	[thread overview]
Message-ID: <52DF9989.5050008@dev.mellanox.co.il> (raw)
In-Reply-To: <1390343288.5567.782.camel@haakon3.risingtidesystems.com>

On 1/22/2014 12:28 AM, Nicholas A. Bellinger wrote:
> On Sun, 2014-01-19 at 14:31 +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 support for DIF protection init/format support into
>>> the FILEIO backend.
>>>
>>> It involves using a seperate $FILE.protection for storing PI that is
>>> opened via fd_init_prot() using the common pi_prot_type attribute.
>>> The actual formatting of the protection is done via fd_format_prot()
>>> using the common pi_prot_format attribute, that will populate the
>>> initial PI data based upon the currently configured pi_prot_type.
>>>
>>> Based on original FILEIO code from Sagi.
>> Nice! see comments below...
>>
>>> v1 changes:
>>>     - Fix sparse warnings in fd_init_format_buf (Fengguang)
>>>
>>> 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/target_core_file.c |  137 +++++++++++++++++++++++++++++++++++++
>>>    drivers/target/target_core_file.h |    4 ++
>>>    2 files changed, 141 insertions(+)
>>>
>>> diff --git a/drivers/target/target_core_file.c b/drivers/target/target_core_file.c
>>> index 0e34cda..119d519 100644
>>> --- a/drivers/target/target_core_file.c
>>> +++ b/drivers/target/target_core_file.c
>>> @@ -700,6 +700,140 @@ static sector_t fd_get_blocks(struct se_device *dev)
>>>    		       dev->dev_attrib.block_size);
>>>    }
>>>    
>>> +static int fd_init_prot(struct se_device *dev)
>>> +{
>>> +	struct fd_dev *fd_dev = FD_DEV(dev);
>>> +	struct file *prot_file, *file = fd_dev->fd_file;
>>> +	struct inode *inode;
>>> +	int ret, flags = O_RDWR | O_CREAT | O_LARGEFILE | O_DSYNC;
>>> +	char buf[FD_MAX_DEV_PROT_NAME];
>>> +
>>> +	if (!file) {
>>> +		pr_err("Unable to locate fd_dev->fd_file\n");
>>> +		return -ENODEV;
>>> +	}
>>> +
>>> +	inode = file->f_mapping->host;
>>> +	if (S_ISBLK(inode->i_mode)) {
>>> +		pr_err("FILEIO Protection emulation only supported on"
>>> +		       " !S_ISBLK\n");
>>> +		return -ENOSYS;
>>> +	}
>>> +
>>> +	if (fd_dev->fbd_flags & FDBD_HAS_BUFFERED_IO_WCE)
>>> +		flags &= ~O_DSYNC;
>>> +
>>> +	snprintf(buf, FD_MAX_DEV_PROT_NAME, "%s.protection",
>>> +		 fd_dev->fd_dev_name);
>>> +
>>> +	prot_file = filp_open(buf, flags, 0600);
>>> +	if (IS_ERR(prot_file)) {
>>> +		pr_err("filp_open(%s) failed\n", buf);
>>> +		ret = PTR_ERR(prot_file);
>>> +		return ret;
>>> +	}
>>> +	fd_dev->fd_prot_file = prot_file;
>>> +
>>> +	return 0;
>>> +}
>>> +
>>> +static void fd_init_format_buf(struct se_device *dev, unsigned char *buf,
>>> +			       u32 unit_size, u32 *ref_tag, u16 app_tag,
>>> +			       bool inc_reftag)
>>> +{
>>> +	unsigned char *p = buf;
>>> +	int i;
>>> +
>>> +	for (i = 0; i < unit_size; i += dev->prot_length) {
>>> +		*((u16 *)&p[0]) = 0xffff;
>>> +		*((__be16 *)&p[2]) = cpu_to_be16(app_tag);
>>> +		*((__be32 *)&p[4]) = cpu_to_be32(*ref_tag);
>>> +
>>> +		if (inc_reftag)
>>> +			(*ref_tag)++;
>>> +
>>> +		p += dev->prot_length;
>>> +	}
>>> +}
>>> +
>>> +static int fd_format_prot(struct se_device *dev)
>>> +{
>>> +	struct fd_dev *fd_dev = FD_DEV(dev);
>>> +	struct file *prot_fd = fd_dev->fd_prot_file;
>>> +	sector_t prot_length, prot;
>>> +	unsigned char *buf;
>>> +	loff_t pos = 0;
>>> +	u32 ref_tag = 0;
>>> +	int unit_size = FDBD_FORMAT_UNIT_SIZE * dev->dev_attrib.block_size;
>>> +	int rc, ret = 0, size, len;
>>> +	bool inc_reftag = false;
>>> +
>>> +	if (!dev->dev_attrib.pi_prot_type) {
>>> +		pr_err("Unable to format_prot while pi_prot_type == 0\n");
>>> +		return -ENODEV;
>>> +	}
>>> +	if (!prot_fd) {
>>> +		pr_err("Unable to locate fd_dev->fd_prot_file\n");
>>> +		return -ENODEV;
>>> +	}
>>> +
>>> +	switch (dev->dev_attrib.pi_prot_type) {
>> redundant - see below.
>>> +	case TARGET_DIF_TYPE3_PROT:
>>> +		ref_tag = 0xffffffff;
>>> +		break;
>>> +	case TARGET_DIF_TYPE2_PROT:
>>> +	case TARGET_DIF_TYPE1_PROT:
>>> +		inc_reftag = true;
>>> +		break;
>>> +	default:
>>> +		break;
>>> +	}
>>> +
>>> +	buf = vzalloc(unit_size);
>>> +	if (!buf) {
>>> +		pr_err("Unable to allocate FILEIO prot buf\n");
>>> +		return -ENOMEM;
>>> +	}
>>> +
>>> +	prot_length = (dev->transport->get_blocks(dev) + 1) * dev->prot_length;
>>> +	size = prot_length;
>>> +
>>> +	pr_debug("Using FILEIO prot_length: %llu\n",
>>> +		 (unsigned long long)prot_length);
>>> +
>>> +	for (prot = 0; prot < prot_length; prot += unit_size) {
>>> +
>>> +		fd_init_format_buf(dev, buf, unit_size, &ref_tag, 0xffff,
>>> +				   inc_reftag);
>> I didn't send you my latest patches (my fault...).T10-PI format should
>> only place
>> escape values throughout the protection file (fill it with 0xff). so I
>> guess in this case
>> fd_init_formast_buf() boils down to memset(buf, 0xff, unit_size) once
>> before the loop
>> and just loop until prot_length writing buf, no need to address
>> apptag/reftag...
> Yeah, was thinking about just formatting with escape values as mentioned
> above, but thought it might be useful to keep around for pre-populating
> values apptag + reftag values for testing purposes.
>
> --nab
>

OK, but maybe it is better to do that under some debug configuration 
rather then always do that.

Sagi.

  reply	other threads:[~2014-01-22 10:12 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
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 [this message]
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=52DF9989.5050008@dev.mellanox.co.il \
    --to=sagig@dev.mellanox.co.il \
    --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=nab@linux-iscsi.org \
    --cc=ogerlitz@mellanox.com \
    --cc=roland@kernel.org \
    --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

Powered by JetHome