All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamal Heib <kheib@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: israelr@nvidia.com, alaa@nvidia.com,
	Sagi Grimberg <sagi@grimberg.me>,
	linux-rdma@vger.kernel.org, jgg@nvidia.com
Subject: Re: [PATCH 1/1] IB/isert: align target max I/O size to initiator size
Date: Tue, 8 Jun 2021 13:24:57 +0300	[thread overview]
Message-ID: <b62e5d29-025a-0827-ecad-a48812114220@redhat.com> (raw)
In-Reply-To: <fdef3991-74e1-63f1-593e-ac2018286ae9@nvidia.com>



On 5/25/21 7:22 PM, Max Gurtovoy wrote:
> 
> On 5/25/2021 6:54 PM, Sagi Grimberg wrote:
>>> Since the Linux iser initiator default max I/O size set to 512KB and
>>> since there is no handshake procedure for this size in iser protocol,
>>> set the default max IO size of the target to 512KB as well.
>>>
>>> For changing the default values, there is a module parameter for both
>>> drivers.
>>
>> Is this solving a bug?
> 
> No. Only OOB for some old connect-IB devices.
> 
> I think it's reasonable to align initiator and target defaults anyway.
> 
> 

Actually, this patch is solving a bug when trying iser over Connect-IB, We see
the following failure when trying to do discovery:

Server:
[  124.264648] infiniband mlx5_0: create_qp:2783:(pid 83): Create QP type 2 failed
[  124.298598] isert: isert_create_qp: rdma_create_qp failed for cma_id -12
[  124.364768] isert: isert_cma_handler: failed handle connect request -12
[  128.271609] infiniband mlx5_0: create_qp:2783:(pid 890): Create QP type 2 failed
[  128.311450] isert: isert_create_qp: rdma_create_qp failed for cma_id -12
[  128.378995] isert: isert_cma_handler: failed handle connect request -12
[  130.668362] infiniband mlx5_0: create_qp:2783:(pid 81): Create QP type 2 failed
[  130.705869] isert: isert_create_qp: rdma_create_qp failed for cma_id -12
[  130.777306] isert: isert_cma_handler: failed handle connect request -12
[  132.671161] infiniband mlx5_0: create_qp:2783:(pid 86): Create QP type 2 failed
[  132.707807] isert: isert_create_qp: rdma_create_qp failed for cma_id -12
[  132.778867] isert: isert_cma_handler: failed handle connect request -12
[  132.810653] infiniband mlx5_0: create_qp:2783:(pid 19): Create QP type 2 failed
[  132.845691] isert: isert_create_qp: rdma_create_qp failed for cma_id -12
[  132.912706] isert: isert_cma_handler: failed handle connect request -12
[  134.681936] infiniband mlx5_0: create_qp:2783:(pid 83): Create QP type 2 failed
[  134.718932] isert: isert_create_qp: rdma_create_qp failed for cma_id -12
[  134.788804] isert: isert_cma_handler: failed handle connect request -12
[  136.678428] infiniband mlx5_0: create_qp:2783:(pid 86): Create QP type 2 failed
[  136.715859] isert: isert_create_qp: rdma_create_qp failed for cma_id -12
[  136.785058] isert: isert_cma_handler: failed handle connect request -12
[  136.817414] infiniband mlx5_0: create_qp:2783:(pid 727): Create QP type 2 failed
[  136.854583] isert: isert_create_qp: rdma_create_qp failed for cma_id -12
[  136.922975] isert: isert_cma_handler: failed handle connect request -12


Client:
$ iscsiadm -m discovery -t sendtargets -p 172.31.0.6 -I iser
iscsiadm: Connection to discovery portal 172.31.0.6 failed: encountered
connection failure
iscsiadm: Connection to discovery portal 172.31.0.6 failed: encountered
connection failure
iscsiadm: Connection to discovery portal 172.31.0.6 failed: encountered
connection failure
iscsiadm: Connection to discovery portal 172.31.0.6 failed: encountered
connection failure
iscsiadm: Connection to discovery portal 172.31.0.6 failed: encountered
connection failure
iscsiadm: Connection to discovery portal 172.31.0.6 failed: encountered
connection failure
iscsiadm: connection login retries (reopen_max) 5 exceeded
iscsiadm: Could not perform SendTargets discovery: iSCSI PDU timed out


Thanks,
Kamal


  reply	other threads:[~2021-06-08 10:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24  8:52 [PATCH 1/1] IB/isert: align target max I/O size to initiator size Max Gurtovoy
2021-05-25 15:54 ` Sagi Grimberg
2021-05-25 16:22   ` Max Gurtovoy
2021-06-08 10:24     ` Kamal Heib [this message]
2021-06-08 11:00       ` Max Gurtovoy
2021-06-08 23:04         ` Sagi Grimberg
2021-06-09  8:45           ` Max Gurtovoy
2021-06-20  8:11             ` Kamal Heib
2021-06-20 11:29               ` Max Gurtovoy
2021-06-22  8:56                 ` Sagi Grimberg
2021-06-22 12:31                   ` Max Gurtovoy
2021-06-23 21:39                     ` Sagi Grimberg
2021-06-24 12:29 ` Jason Gunthorpe

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=b62e5d29-025a-0827-ecad-a48812114220@redhat.com \
    --to=kheib@redhat.com \
    --cc=alaa@nvidia.com \
    --cc=israelr@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=sagi@grimberg.me \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.