public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Nicholas A. Bellinger"
	<nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>,
	Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	tzahio-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH RFC v2 00/10] Introduce Signature feature
Date: Tue, 5 Nov 2013 11:13:22 +0200	[thread overview]
Message-ID: <5278B6B2.1010006@mellanox.com> (raw)
In-Reply-To: <1383590471.4216.22.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>

On 11/4/2013 8:41 PM, Nicholas A. Bellinger wrote:
> On Sat, 2013-11-02 at 14:57 -0700, Bart Van Assche wrote:
>> On 1/11/2013 18:36, Nicholas A. Bellinger wrote:
>>> On Fri, 2013-11-01 at 08:03 -0700, Bart Van Assche wrote:
>>>> On 31/10/2013 5:24, Sagi Grimberg wrote:
>>>>> In T10-DIF, when a series of 512-byte data blocks are transferred, each
>>>>> block is followed by an 8-byte guard. The guard consists of CRC that
>>>>> protects the integrity of the data in the block, and some other tags
>>>>> that protects against mis-directed IOs.
>>>> Shouldn't that read "logical block length divided by 2**(protection
>>>> interval exponent)" instead of "512" ? From the SPC-4 FORMAT UNIT
>>>> section:
>>> Why should the protection interval in FORMAT_UNIT be mentioned when it's
>>> not supported by the hardware, nor by drivers/scsi/sd_dif.c itself..?
>> Hello Nick,
>>
>> My understanding is that this patch series is not only intended for
>> initiator drivers but also for target drivers like ib_srpt and ib_isert.
>> As you know target drivers do not restrict the initiator operating
>> system to Linux. Although I do not know whether there are already
>> operating systems that support the "protection interval exponent",
> It's my understanding that Linux is still the only stack that supports
> DIF, so AFAICT no one is actually supporting this.
>
>>   I think it is a good idea to stay as close as possible to the terminology
>> of the SPC-4 standard.
>>
> No, in this context it only adds pointless misdirection because 1) The
> hardware in question doesn't support it, and 2) Linux itself doesn't
> support it.

I think that Bart is suggesting renaming block_size as pi_interval in 
ib_sig_domain.
I tend to agree since even if support for that does not exist yet, it 
might be in the future.
I think it is not a misdirection because it does represent the 
protection information interval.

> --nab
>

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-11-05  9:13 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 12:24 [PATCH RFC v2 00/10] Introduce Signature feature Sagi Grimberg
     [not found] ` <1383222255-22699-1-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31 12:24   ` [PATCH RFC v2 01/10] IB/core: Introduce protected memory regions Sagi Grimberg
     [not found]     ` <1383222255-22699-2-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-01 17:09       ` Bart Van Assche
     [not found]         ` <5273E03C.3010501-HInyCGIudOg@public.gmane.org>
2013-11-03 12:14           ` Sagi Grimberg
2013-10-31 12:24   ` [PATCH RFC v2 02/10] IB/core: Introduce Signature Verbs API Sagi Grimberg
     [not found]     ` <1383222255-22699-3-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-01 15:13       ` Bart Van Assche
     [not found]         ` <5273C4FC.4070708-HInyCGIudOg@public.gmane.org>
2013-11-03 12:15           ` Sagi Grimberg
2013-11-01 18:46       ` Bart Van Assche
     [not found]         ` <5273F6F4.3000300-HInyCGIudOg@public.gmane.org>
2013-11-03 12:15           ` Sagi Grimberg
     [not found]             ` <52763E68.2040605-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-03 14:41               ` Bart Van Assche
     [not found]                 ` <5276608D.2020605-HInyCGIudOg@public.gmane.org>
2013-11-03 16:30                   ` Sagi Grimberg
2013-11-01 22:23       ` Bart Van Assche
     [not found]         ` <527429E7.7010705-HInyCGIudOg@public.gmane.org>
2013-11-03 12:16           ` Sagi Grimberg
2013-10-31 12:24   ` [PATCH RFC v2 03/10] IB/mlx5, mlx5_core: Support for create_mr and destroy_mr Sagi Grimberg
     [not found]     ` <1383222255-22699-4-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31 12:52       ` Jack Wang
     [not found]         ` <52725299.7020105-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-31 12:59           ` Sagi Grimberg
2013-10-31 12:24   ` [PATCH RFC v2 04/10] IB/mlx5: Initialize mlx5_ib_qp signature related Sagi Grimberg
2013-10-31 12:24   ` [PATCH RFC v2 05/10] IB/mlx5: Break wqe handling to begin & finish routines Sagi Grimberg
2013-10-31 12:24   ` [PATCH RFC v2 06/10] IB/mlx5: remove MTT access mode from umr flags helper function Sagi Grimberg
2013-10-31 12:24   ` [PATCH RFC v2 07/10] IB/mlx5: Keep mlx5 MRs in a radix tree under device Sagi Grimberg
     [not found]     ` <1383222255-22699-8-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-01 20:46       ` Bart Van Assche
     [not found]         ` <5274131C.90601-HInyCGIudOg@public.gmane.org>
2013-11-03 12:16           ` Sagi Grimberg
     [not found]             ` <52763E88.4050300-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-03 13:40               ` Or Gerlitz
2013-10-31 12:24   ` [PATCH RFC v2 08/10] IB/mlx5: Support IB_WR_REG_SIG_MR Sagi Grimberg
     [not found]     ` <1383222255-22699-9-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31 13:01       ` Jack Wang
2013-11-01 15:05       ` Bart Van Assche
     [not found]         ` <5273C32E.2020405-HInyCGIudOg@public.gmane.org>
2013-11-03 12:16           ` Sagi Grimberg
2013-11-01 20:37       ` Bart Van Assche
     [not found]         ` <527410F3.6040704-HInyCGIudOg@public.gmane.org>
2013-11-02 19:21           ` Or Gerlitz
     [not found]             ` <CAJZOPZLnyqzzx91ohmW+exy0k8g-FX6reSBCGmh_F2tTGWWOog-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-02 21:59               ` Bart Van Assche
     [not found]                 ` <527575D0.9050802-HInyCGIudOg@public.gmane.org>
2013-11-03 12:20                   ` Sagi Grimberg
2013-10-31 12:24   ` [PATCH RFC v2 09/10] IB/mlx5: Collect signature error completion Sagi Grimberg
2013-10-31 12:24   ` [PATCH RFC v2 10/10] IB/mlx5: Publish support in signature feature Sagi Grimberg
2013-10-31 12:55   ` [PATCH RFC v2 00/10] Introduce Signature feature Jack Wang
     [not found]     ` <5272535D.4090805-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-31 13:20       ` Sagi Grimberg
     [not found]         ` <52725930.7030702-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31 13:29           ` Jack Wang
2013-11-01 15:03   ` Bart Van Assche
     [not found]     ` <5273C2B6.7010901-HInyCGIudOg@public.gmane.org>
2013-11-02  1:36       ` Nicholas A. Bellinger
     [not found]         ` <1383356167.4216.16.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2013-11-02 21:57           ` Bart Van Assche
     [not found]             ` <52757555.6090907-HInyCGIudOg@public.gmane.org>
2013-11-04 18:41               ` Nicholas A. Bellinger
     [not found]                 ` <1383590471.4216.22.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2013-11-05  9:13                   ` Sagi Grimberg [this message]
     [not found]                     ` <5278B6B2.1010006-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-05 18:30                       ` Nicholas A. Bellinger
2013-11-01 22:06   ` Bart Van Assche
     [not found]     ` <527425DA.7040609-HInyCGIudOg@public.gmane.org>
2013-11-03 12:13       ` Sagi Grimberg
2013-11-03 12:14       ` 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=5278B6B2.1010006@mellanox.com \
    --to=sagig-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=bvanassche-HInyCGIudOg@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org \
    --cc=oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=tzahio-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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