All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH v2 03/12] svcrdma: Update max_send_sges after QP is created
Date: Sun, 04 Feb 2024 18:16:50 -0500	[thread overview]
Message-ID: <170708861056.28128.2372400452643006250.stgit@bazille.1015granger.net> (raw)
In-Reply-To: <170708844422.28128.2979813721958631192.stgit@bazille.1015granger.net>

From: Chuck Lever <chuck.lever@oracle.com>

rdma_create_qp() can modify cap.max_send_sges. Copy the new value
to the svcrdma transport so it is bound by the new limit instead
of the requested one.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 net/sunrpc/xprtrdma/svc_rdma_transport.c |    1 +
 1 file changed, 1 insertion(+)

diff --git a/net/sunrpc/xprtrdma/svc_rdma_transport.c b/net/sunrpc/xprtrdma/svc_rdma_transport.c
index 8be0493797cf..839c0e80e5cd 100644
--- a/net/sunrpc/xprtrdma/svc_rdma_transport.c
+++ b/net/sunrpc/xprtrdma/svc_rdma_transport.c
@@ -467,6 +467,7 @@ static struct svc_xprt *svc_rdma_accept(struct svc_xprt *xprt)
 		trace_svcrdma_qp_err(newxprt, ret);
 		goto errout;
 	}
+	newxprt->sc_max_send_sges = qp_attr.cap.max_send_sge;
 	newxprt->sc_qp = newxprt->sc_cm_id->qp;
 
 	if (!(dev->attrs.device_cap_flags & IB_DEVICE_MEM_MGT_EXTENSIONS))



  parent reply	other threads:[~2024-02-04 23:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04 23:16 [PATCH v2 00/12] NFSD RDMA transport improvements Chuck Lever
2024-02-04 23:16 ` [PATCH v2 01/12] svcrdma: Reserve an extra WQE for ib_drain_rq() Chuck Lever
2024-02-04 23:16 ` [PATCH v2 02/12] svcrdma: Report CQ depths in debugging output Chuck Lever
2024-02-04 23:16 ` Chuck Lever [this message]
2024-02-04 23:16 ` [PATCH v2 04/12] svcrdma: Increase the per-transport rw_ctx count Chuck Lever
2024-02-04 23:17 ` [PATCH v2 05/12] svcrdma: Fix SQ wake-ups Chuck Lever
2024-02-04 23:17 ` [PATCH v2 06/12] svcrdma: Prevent a UAF in svc_rdma_send() Chuck Lever
2024-02-04 23:17 ` [PATCH v2 07/12] svcrdma: Fix retry loop " Chuck Lever
2024-02-04 23:17 ` [PATCH v2 08/12] svcrdma: Post Send WR chain Chuck Lever
2024-02-04 23:17 ` [PATCH v2 09/12] svcrdma: Move write_info for Reply chunks into struct svc_rdma_send_ctxt Chuck Lever
2024-02-04 23:17 ` [PATCH v2 10/12] svcrdma: Post the Reply chunk and Send WR together Chuck Lever
2024-02-04 23:17 ` [PATCH v2 11/12] svcrdma: Post WRs for Write chunks in svc_rdma_sendto() Chuck Lever
2024-02-04 23:17 ` [PATCH v2 12/12] svcrdma: Add Write chunk WRs to the RPC's Send WR chain Chuck Lever

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=170708861056.28128.2372400452643006250.stgit@bazille.1015granger.net \
    --to=cel@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.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 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.