From: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> To: Parav Pandit <parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org> Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Linux NFS Mailing List <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: Re: [PATCH v1 4/5] xprtrdma: Reduce required number of send SGEs Date: Fri, 13 Jan 2017 13:30:56 -0500 [thread overview] Message-ID: <706404D7-A179-4E54-A2C7-534FCC1B5745@oracle.com> (raw) In-Reply-To: <VI1PR0502MB30080923A8B244BBAD059358D1780-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org> > On Jan 13, 2017, at 1:01 PM, Parav Pandit <parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org> wrote: > > Hi Chuck, > >> -----Original Message----- >> From: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:linux-rdma- >> owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of Chuck Lever >> Sent: Friday, January 13, 2017 11:43 AM >> To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org >> Subject: [PATCH v1 4/5] xprtrdma: Reduce required number of send SGEs >> diff --git a/net/sunrpc/xprtrdma/rpc_rdma.c >> b/net/sunrpc/xprtrdma/rpc_rdma.c index 4909758..ab699f9 100644 > >> /* The client can't know how large the actual reply will be. Thus it diff --git >> a/net/sunrpc/xprtrdma/verbs.c b/net/sunrpc/xprtrdma/verbs.c index >> 12e8242..5dcdd0b 100644 >> --- a/net/sunrpc/xprtrdma/verbs.c >> +++ b/net/sunrpc/xprtrdma/verbs.c >> @@ -488,18 +488,19 @@ static void rpcrdma_destroy_id(struct rdma_cm_id >> *id) >> */ >> int >> rpcrdma_ep_create(struct rpcrdma_ep *ep, struct rpcrdma_ia *ia, >> - struct rpcrdma_create_data_internal *cdata) >> + struct rpcrdma_create_data_internal *cdata) >> { >> struct rpcrdma_connect_private *pmsg = &ep->rep_cm_private; >> + unsigned int max_qp_wr, max_sge; >> struct ib_cq *sendcq, *recvcq; >> - unsigned int max_qp_wr; >> int rc; >> >> - if (ia->ri_device->attrs.max_sge < RPCRDMA_MAX_SEND_SGES) { >> - dprintk("RPC: %s: insufficient sge's available\n", >> - __func__); >> + max_sge = min(ia->ri_device->attrs.max_sge, >> RPCRDMA_MAX_SEND_SGES); >> + if (max_sge < 3) { >> + pr_warn("rpcrdma: HCA provides only %d send SGEs\n", >> max_sge); >> return -ENOMEM; >> } >> + ia->ri_max_sgeno = max_sge - 3; >> > > I didn't noticed this new ri_max_sgeno variable being used in this patch set. Did I miss? Yes, you snipped out the other hunk where it is used. > You also might want to rename it to ri_max_sge_num. > Regardless for some device with 3 SGEs, ri_max_sgeno will become zero. Is that fine? Yes, that's OK, and tested. Zero means that NFS WRITE and SYMLINK payloads will always be sent in a Read chunk. > You wanted to check for value of 5? > It would be good to have define for this minimum required 3 SGEs header file such as RPCRDMA_MIN_REQ_RECV_SGE. OK. > > >> if (ia->ri_device->attrs.max_qp_wr <= RPCRDMA_BACKWARD_WRS) { >> dprintk("RPC: %s: insufficient wqe's available\n", >> @@ -524,7 +525,7 @@ static void rpcrdma_destroy_id(struct rdma_cm_id >> *id) >> ep->rep_attr.cap.max_recv_wr = cdata->max_requests; >> ep->rep_attr.cap.max_recv_wr += RPCRDMA_BACKWARD_WRS; >> ep->rep_attr.cap.max_recv_wr += 1; /* drain cqe */ >> - ep->rep_attr.cap.max_send_sge = RPCRDMA_MAX_SEND_SGES; >> + ep->rep_attr.cap.max_send_sge = max_sge; >> ep->rep_attr.cap.max_recv_sge = 1; >> ep->rep_attr.cap.max_inline_data = 0; >> ep->rep_attr.sq_sig_type = IB_SIGNAL_REQ_WR; diff --git >> a/net/sunrpc/xprtrdma/xprt_rdma.h b/net/sunrpc/xprtrdma/xprt_rdma.h >> index f495df0c..c134d0b 100644 >> --- a/net/sunrpc/xprtrdma/xprt_rdma.h >> +++ b/net/sunrpc/xprtrdma/xprt_rdma.h >> @@ -74,6 +74,7 @@ struct rpcrdma_ia { >> unsigned int ri_max_frmr_depth; >> unsigned int ri_max_inline_write; >> unsigned int ri_max_inline_read; >> + unsigned int ri_max_sgeno; >> bool ri_reminv_expected; >> bool ri_implicit_padding; >> enum ib_mr_type ri_mrtype; >> >> -- >> 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 > N§ēæėrļyúčØbēXŽķĮ§vØ^)Þš{.nĮ+·Ĩ{ąŲ{ayš\x1d ĘÚë,j\aĒfĢĒ·hāzđ\x1e ŪwĨĒļ\f Ē·Ķj:+vĻwčjØmķĸū\aŦęįzZ+ųÝĒj"ú! -- Chuck Lever -- 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
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Lever <chuck.lever@oracle.com> To: Parav Pandit <parav@mellanox.com> Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>, Linux NFS Mailing List <linux-nfs@vger.kernel.org> Subject: Re: [PATCH v1 4/5] xprtrdma: Reduce required number of send SGEs Date: Fri, 13 Jan 2017 13:30:56 -0500 [thread overview] Message-ID: <706404D7-A179-4E54-A2C7-534FCC1B5745@oracle.com> (raw) In-Reply-To: <VI1PR0502MB30080923A8B244BBAD059358D1780@VI1PR0502MB3008.eurprd05.prod.outlook.com> > On Jan 13, 2017, at 1:01 PM, Parav Pandit <parav@mellanox.com> wrote: > > Hi Chuck, > >> -----Original Message----- >> From: linux-rdma-owner@vger.kernel.org [mailto:linux-rdma- >> owner@vger.kernel.org] On Behalf Of Chuck Lever >> Sent: Friday, January 13, 2017 11:43 AM >> To: linux-rdma@vger.kernel.org; linux-nfs@vger.kernel.org >> Subject: [PATCH v1 4/5] xprtrdma: Reduce required number of send SGEs >> diff --git a/net/sunrpc/xprtrdma/rpc_rdma.c >> b/net/sunrpc/xprtrdma/rpc_rdma.c index 4909758..ab699f9 100644 > >> /* The client can't know how large the actual reply will be. Thus it diff --git >> a/net/sunrpc/xprtrdma/verbs.c b/net/sunrpc/xprtrdma/verbs.c index >> 12e8242..5dcdd0b 100644 >> --- a/net/sunrpc/xprtrdma/verbs.c >> +++ b/net/sunrpc/xprtrdma/verbs.c >> @@ -488,18 +488,19 @@ static void rpcrdma_destroy_id(struct rdma_cm_id >> *id) >> */ >> int >> rpcrdma_ep_create(struct rpcrdma_ep *ep, struct rpcrdma_ia *ia, >> - struct rpcrdma_create_data_internal *cdata) >> + struct rpcrdma_create_data_internal *cdata) >> { >> struct rpcrdma_connect_private *pmsg = &ep->rep_cm_private; >> + unsigned int max_qp_wr, max_sge; >> struct ib_cq *sendcq, *recvcq; >> - unsigned int max_qp_wr; >> int rc; >> >> - if (ia->ri_device->attrs.max_sge < RPCRDMA_MAX_SEND_SGES) { >> - dprintk("RPC: %s: insufficient sge's available\n", >> - __func__); >> + max_sge = min(ia->ri_device->attrs.max_sge, >> RPCRDMA_MAX_SEND_SGES); >> + if (max_sge < 3) { >> + pr_warn("rpcrdma: HCA provides only %d send SGEs\n", >> max_sge); >> return -ENOMEM; >> } >> + ia->ri_max_sgeno = max_sge - 3; >> > > I didn't noticed this new ri_max_sgeno variable being used in this patch set. Did I miss? Yes, you snipped out the other hunk where it is used. > You also might want to rename it to ri_max_sge_num. > Regardless for some device with 3 SGEs, ri_max_sgeno will become zero. Is that fine? Yes, that's OK, and tested. Zero means that NFS WRITE and SYMLINK payloads will always be sent in a Read chunk. > You wanted to check for value of 5? > It would be good to have define for this minimum required 3 SGEs header file such as RPCRDMA_MIN_REQ_RECV_SGE. OK. > > >> if (ia->ri_device->attrs.max_qp_wr <= RPCRDMA_BACKWARD_WRS) { >> dprintk("RPC: %s: insufficient wqe's available\n", >> @@ -524,7 +525,7 @@ static void rpcrdma_destroy_id(struct rdma_cm_id >> *id) >> ep->rep_attr.cap.max_recv_wr = cdata->max_requests; >> ep->rep_attr.cap.max_recv_wr += RPCRDMA_BACKWARD_WRS; >> ep->rep_attr.cap.max_recv_wr += 1; /* drain cqe */ >> - ep->rep_attr.cap.max_send_sge = RPCRDMA_MAX_SEND_SGES; >> + ep->rep_attr.cap.max_send_sge = max_sge; >> ep->rep_attr.cap.max_recv_sge = 1; >> ep->rep_attr.cap.max_inline_data = 0; >> ep->rep_attr.sq_sig_type = IB_SIGNAL_REQ_WR; diff --git >> a/net/sunrpc/xprtrdma/xprt_rdma.h b/net/sunrpc/xprtrdma/xprt_rdma.h >> index f495df0c..c134d0b 100644 >> --- a/net/sunrpc/xprtrdma/xprt_rdma.h >> +++ b/net/sunrpc/xprtrdma/xprt_rdma.h >> @@ -74,6 +74,7 @@ struct rpcrdma_ia { >> unsigned int ri_max_frmr_depth; >> unsigned int ri_max_inline_write; >> unsigned int ri_max_inline_read; >> + unsigned int ri_max_sgeno; >> bool ri_reminv_expected; >> bool ri_implicit_padding; >> enum ib_mr_type ri_mrtype; >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the >> body of a message to majordomo@vger.kernel.org More majordomo info at >> http://vger.kernel.org/majordomo-info.html > N§ēæėrļyúčØbēXŽķĮ§vØ^)Þš{.nĮ+·Ĩ{ąŲ{ayš\x1dĘÚë,j\aĒfĢĒ·hāzđ\x1eŪwĨĒļ\fĒ·Ķj:+vĻwčjØmķĸū\aŦęįzZ+ųÝĒj"ú! -- Chuck Lever
next prev parent reply other threads:[~2017-01-13 18:30 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-01-13 17:42 [PATCH v1 0/5] Fix "support large inline thresholds" Chuck Lever 2017-01-13 17:42 ` Chuck Lever [not found] ` <20170113173023.32692.30661.stgit-FYjufvaPoItvLzlybtyyYzGyq/o6K9yX@public.gmane.org> 2017-01-13 17:42 ` [PATCH v1 1/5] xprtrdma: Fix Read chunk padding Chuck Lever 2017-01-13 17:42 ` Chuck Lever 2017-01-13 17:43 ` [PATCH v1 2/5] xprtrdma: Per-connection pad optimization Chuck Lever 2017-01-13 17:43 ` Chuck Lever 2017-01-13 17:43 ` [PATCH v1 3/5] xprtrdma: Disable pad optimization by default Chuck Lever 2017-01-13 17:43 ` Chuck Lever 2017-01-13 17:43 ` [PATCH v1 4/5] xprtrdma: Reduce required number of send SGEs Chuck Lever 2017-01-13 17:43 ` Chuck Lever [not found] ` <20170113174322.32692.66126.stgit-FYjufvaPoItvLzlybtyyYzGyq/o6K9yX@public.gmane.org> 2017-01-13 18:01 ` Parav Pandit 2017-01-13 18:01 ` Parav Pandit [not found] ` <VI1PR0502MB30080923A8B244BBAD059358D1780-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org> 2017-01-13 18:30 ` Chuck Lever [this message] 2017-01-13 18:30 ` Chuck Lever [not found] ` <706404D7-A179-4E54-A2C7-534FCC1B5745-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> 2017-01-13 19:14 ` Parav Pandit 2017-01-13 19:14 ` Parav Pandit 2017-01-13 17:43 ` [PATCH v1 5/5] xprtrdma: Shrink send SGEs array Chuck Lever 2017-01-13 17:43 ` Chuck Lever 2017-01-20 17:30 ` [PATCH v1 0/5] Fix "support large inline thresholds" Steve Wise 2017-01-20 17:30 ` Steve Wise 2017-01-20 18:17 ` Chuck Lever 2017-01-20 18:17 ` 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=706404D7-A179-4E54-A2C7-534FCC1B5745@oracle.com \ --to=chuck.lever-qhclzuegtsvqt0dzr+alfa@public.gmane.org \ --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=parav-VPRAkNaXOzVWk0Htik3J/w@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: linkBe 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.