On 1/24/2015 6:54 PM, Or Gerlitz wrote:
On Fri, Jan 23, 2015 at 10:15 PM, Mike Christie <[email protected]
<mailto:[email protected]>>wrote:
On 01/23/2015 01:20 AM, Or Gerlitz wrote:
> I don't think we need to go for so many changes in libiscsi and such
> just for that. But let us 1st understand what exactly is sent to the
> target as MRDSL in that case.
>
Missed this question.
It will be 8K.
Before we do login negotiation, we override the user specified
MRDSL if
the driver cannot support (iscsi_copy_operational_param() call in
other
mail).
When login.c:():fill_op_params_text() is run during negotiation we
then
use that safe value.
Got it, so the target should be seeing an advertized value of 8KB for
MRDSL. I will verify that.
OK, Mike - this is goes just as you described... for kernel transport
iscsid caps the MRDSL down to 8KB. We did manage to run discovery over
iser for ST payload > 8KB w.o touching iscsid.conf -- we just previously
were hitting some bugs on the target side (SCST iser driver), Yan fixed
them and it's working fine now. No action is needed on the initiator side.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
