Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Akinobu Mita <akinobu.mita@gmail.com>, target-devel@vger.kernel.org
Cc: Tim Chen <tim.c.chen@linux.intel.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org,
	Nicholas Bellinger <nab@linux-iscsi.org>,
	Sagi Grimberg <sagig@mellanox.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v3 0/5] target: Fix several problems related to T10-PI support
Date: Sun, 26 Apr 2015 13:33:43 +0300	[thread overview]
Message-ID: <553CBF07.6080902@dev.mellanox.co.il> (raw)
In-Reply-To: <1429972410-7146-1-git-send-email-akinobu.mita@gmail.com>

On 4/25/2015 5:33 PM, Akinobu Mita wrote:
> This patchset aims to fix several problems related to T10-PI support.
>
> These patches can be applied on top of Sagi's "[v1] Simlify dif_verify
> routines and fixup fileio protection information code" patchset.
>

Hi Akinobu,

I have given this some more thought,

This set adds DIF protected WRITE_SAME support. I don't think this
will work with a real transport that offload DIF computation (at least
not over RDMA - perhaps qlogic/emulex folks can comment on their
devices).

The problem is that the HBA does not have the write_same functionality
you introduce here, i.e. generate multiple same protection fields for a
single data block.

We can require the fabrics drivers to do that (probably compensate in
SW) or, we can have the write_same logic to live only in the
core/backend code.

In this case, for WRITE_SAME, have the fabrics generate/verify a single
data block (one integrity field) like they do today, and then the core
will expand it to the correct number of sectors using some form of
sbc_dif_expand_same()

I'm not sure which way is better...

Martin? Nic? Thoughts?

  parent reply	other threads:[~2015-04-26 10:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25 14:33 [PATCH v3 0/5] target: Fix several problems related to T10-PI support Akinobu Mita
2015-04-25 14:33 ` [PATCH v3 2/5] lib: introduce crc_t10dif_update() Akinobu Mita
2015-04-27 23:41   ` Martin K. Petersen
2015-04-28 17:38   ` Tim Chen
2015-04-28 23:07     ` Martin K. Petersen
2015-04-29  0:39     ` Akinobu Mita
2015-04-29  0:49     ` Herbert Xu
2015-04-29 16:07       ` Tim Chen
2015-04-25 14:33 ` [PATCH v3 3/5] target: handle odd SG mapping for data transfer memory Akinobu Mita
2015-04-26 10:07   ` Sagi Grimberg
2015-04-27 13:03     ` Akinobu Mita
2015-04-26 10:33 ` Sagi Grimberg [this message]
2015-04-27 23:50   ` [PATCH v3 0/5] target: Fix several problems related to T10-PI support Martin K. Petersen
2015-04-28 10:22     ` Sagi Grimberg
2015-04-28 23:06       ` Martin K. Petersen

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=553CBF07.6080902@dev.mellanox.co.il \
    --to=sagig@dev.mellanox.co.il \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akinobu.mita@gmail.com \
    --cc=davem@davemloft.net \
    --cc=hch@lst.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=nab@linux-iscsi.org \
    --cc=sagig@mellanox.com \
    --cc=target-devel@vger.kernel.org \
    --cc=tim.c.chen@linux.intel.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