From: Leon Romanovsky <leonro@mellanox.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org,
Laurence Oberman <loberman@redhat.com>,
Kamal Heib <kamalheib1@gmail.com>
Subject: Re: [PATCH v2 4/4] RDMA/srpt: Increase max_send_sge
Date: Mon, 25 May 2020 20:51:52 +0300 [thread overview]
Message-ID: <20200525175152.GI10591@unreal> (raw)
In-Reply-To: <20200525172212.14413-5-bvanassche@acm.org>
On Mon, May 25, 2020 at 10:22:12AM -0700, Bart Van Assche wrote:
> The ib_srpt driver limits max_send_sge to 16. Since that is a workaround
> for an mlx4 bug that has been fixed, increase max_send_sge. For mlx4, do
> not use the value advertised by the driver (32) since that causes QP's
> to transition to the error status.
Bart,
How are you avoiding mlx4 bug in this patch?
Isn't "attrs->max_send_sge" come from driver as is?
Thanks
>
> See also commit f95ccffc715b ("IB/mlx4: Use 4K pages for kernel QP's WQE
> buffer").
>
> Cc: Laurence Oberman <loberman@redhat.com>
> Cc: Kamal Heib <kamalheib1@gmail.com>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
> drivers/infiniband/ulp/srpt/ib_srpt.c | 3 +--
> drivers/infiniband/ulp/srpt/ib_srpt.h | 5 -----
> 2 files changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/infiniband/ulp/srpt/ib_srpt.c b/drivers/infiniband/ulp/srpt/ib_srpt.c
> index 1ad3cc7c553a..86e4c87e7ec2 100644
> --- a/drivers/infiniband/ulp/srpt/ib_srpt.c
> +++ b/drivers/infiniband/ulp/srpt/ib_srpt.c
> @@ -1816,8 +1816,7 @@ static int srpt_create_ch_ib(struct srpt_rdma_ch *ch)
> */
> qp_init->cap.max_send_wr = min(sq_size / 2, attrs->max_qp_wr);
> qp_init->cap.max_rdma_ctxs = sq_size / 2;
> - qp_init->cap.max_send_sge = min(attrs->max_send_sge,
> - SRPT_MAX_SG_PER_WQE);
> + qp_init->cap.max_send_sge = attrs->max_send_sge;
> qp_init->cap.max_recv_sge = 1;
> qp_init->port_num = ch->sport->port;
> if (sdev->use_srq)
> diff --git a/drivers/infiniband/ulp/srpt/ib_srpt.h b/drivers/infiniband/ulp/srpt/ib_srpt.h
> index 2e1a69840857..f31c349d07a1 100644
> --- a/drivers/infiniband/ulp/srpt/ib_srpt.h
> +++ b/drivers/infiniband/ulp/srpt/ib_srpt.h
> @@ -105,11 +105,6 @@ enum {
> SRP_CMD_ACA = 0x4,
>
> SRPT_DEF_SG_TABLESIZE = 128,
> - /*
> - * An experimentally determined value that avoids that QP creation
> - * fails due to "swiotlb buffer is full" on systems using the swiotlb.
> - */
> - SRPT_MAX_SG_PER_WQE = 16,
>
> MIN_SRPT_SQ_SIZE = 16,
> DEF_SRPT_SQ_SIZE = 4096,
next prev parent reply other threads:[~2020-05-25 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 17:22 [PATCH v2 0/4] Four SRP initiator and target patches Bart Van Assche
2020-05-25 17:22 ` [PATCH v2 1/4] RDMA/srp: Make the channel count configurable per target Bart Van Assche
2020-05-25 17:22 ` [PATCH v2 2/4] RDMA/srpt: Make debug output more detailed Bart Van Assche
2020-05-25 17:22 ` [PATCH v2 3/4] RDMA/srpt: Reduce max_recv_sge to 1 Bart Van Assche
2020-05-25 17:22 ` [PATCH v2 4/4] RDMA/srpt: Increase max_send_sge Bart Van Assche
2020-05-25 17:51 ` Leon Romanovsky [this message]
2020-05-25 19:15 ` Bart Van Assche
2020-05-25 21:51 ` Bart Van Assche
2020-05-26 5:55 ` Leon Romanovsky
2020-05-29 18:14 ` [PATCH v2 0/4] Four SRP initiator and target patches 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=20200525175152.GI10591@unreal \
--to=leonro@mellanox.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kamalheib1@gmail.com \
--cc=linux-rdma@vger.kernel.org \
--cc=loberman@redhat.com \
/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