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: Tue, 21 Jul 2015 08:35:46 -0700 [thread overview]
Message-ID: <55AE66D2.7050206@sandisk.com> (raw)
In-Reply-To: <55AE0E30.40404-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On 07/21/2015 02:17 AM, Sagi Grimberg wrote:
> Also, what is the imm_length? hard-coded? or do you specify that in the
> login request as well? if so, is the target allowed to lower that value
> (i.e. is it negotiable)?
Hello Sagi,
As you probably know SRP initiator and target drivers negotiate the
MAXIMUM INITIATOR TO TARGET IU LENGTH (MITTIL) and MAXIMUM TARGET TO
INITIATOR IU LENGTH (MTTIIL) parameters during login. The choice we made
is that the initiator must only send immediate data if the size of the
resulting message does not exceed the MITTIL. Since an SRP target driver
is only allowed to send back a MITTIL value that is larger than or equal
to what an initiator requested, the maximum immediate data size is
controlled by the target driver.
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
prev parent reply other threads:[~2015-07-21 15:35 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] ` <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
[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
[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 [this message]
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=55AE66D2.7050206@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