public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: Sagi Grimberg
	<sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: RFC: Immediate data support for SRP
Date: Mon, 20 Jul 2015 17:03:06 -0700	[thread overview]
Message-ID: <55AD8C3A.9070403@sandisk.com> (raw)
In-Reply-To: <55ABCB34.1000506-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>

On 07/19/2015 09:07 AM, Sagi Grimberg wrote:
> On 7/16/2015 6:25 PM, Bart Van Assche wrote:
>> As you probably know for write requests "immediate data" means sending
>> the data in the same packet as the write command instead of sending it
>> as a separate packet. This approach improves performance and reduces
>> latency. Although support for immediate data has not been standardized,
>
> Has anyone tried to get it into the standard? It would seem beneficial
> to just add it. I wouldn't want this to be a Linux compatible only
> feature...

Earlier today I have asked the SanDisk representative in the ANSI T10 
committee for his opinion about standardizing support for immediate data 
for the SRP protocol. I'm now waiting for his reply.

>> it is easy to add to the SRP initiator and target drivers.
>> Implementations exist in the ib_srp-backport initiator driver and the
>> SCST SRP target driver (see also
>> https://github.com/bvanassche/ib_srp-backport and
>> http://sourceforge.net/p/scst/svn/HEAD/tree/trunk/srpt/). These
>> implementations are available since considerable time, work reliably,
>> are backwards compatible and support zero-copy. Since using immediate
>> data provides a measurable performance improvement I'm wondering whether
>> it would be acceptable to add support for immediate data to the SRP
>> drivers in the Linux kernel tree (ib_srp and ib_srpt) ?
>
> Was this tested against any other array besides SCST and LIO? I know
> people are using SRP against various arrays (Oracle ZFS, RamSan TMS,
> DDN Fusion, NIMBUS, NetApp E5400A...). Their not running upstream
> kernels, but they will catch up at some point...

Not yet, but the existing implementation is backwards compatible. The 
SRP initiator sets a flag in the login request to request the target 
driver to enable immediate data (SRP_BUF_FORMAT_IMM), and only if the 
target driver sends a login response in which the same flag is set 
immediate data is enabled. Immediate data could only be enabled when it 
should not be enabled if an SRP target sets other flags in its login 
reply than those that have been standardized by the ANSI T10 committee.

Bart.

--
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:[~2015-07-21  0:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 15:25 RFC: Immediate data support for SRP Bart Van Assche
     [not found] ` <55A7CCF1.3080201-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-07-19 16:07   ` Sagi Grimberg
     [not found]     ` <55ABCB34.1000506-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-07-19 21:43       ` Or Gerlitz
     [not found]         ` <CAJ3xEMiz=n_uP9TQ6YsGN+omzsN3Zrz5skDEq00+fE188z0erA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-20  9:44           ` Sagi Grimberg
     [not found]             ` <55ACC2FA.8030202-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-07-20 15:26               ` Or Gerlitz
     [not found]                 ` <55AD133D.2040204-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-07-21  9:25                   ` Sagi Grimberg
2015-07-21  0:03       ` Bart Van Assche [this message]
     [not found]         ` <55AD8C3A.9070403-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-07-21  9:17           ` Sagi Grimberg
     [not found]             ` <55AE0E30.40404-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-07-21 15:35               ` Bart Van Assche
     [not found]     ` <CACaajQu9QBo7robmrFF7hev-xS=c3VD9qQTn5DKuuObk5aU_Kg@mail.gmail.com>
     [not found]       ` <CACaajQu9QBo7robmrFF7hev-xS=c3VD9qQTn5DKuuObk5aU_Kg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-20 23:49         ` Bart Van Assche

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=55AD8C3A.9070403@sandisk.com \
    --to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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