From: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux NFS Mailing List
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 9/9] svcrdma: Use new CQ API for RPC-over-RDMA server send CQs
Date: Thu, 11 Feb 2016 13:48:54 -0500 [thread overview]
Message-ID: <46CB2961-FCAC-4901-B66C-B7B6503ADDF3@oracle.com> (raw)
In-Reply-To: <01d001d164fc$78fae5e0$6af0b1a0$@opengridcomputing.com>
> On Feb 11, 2016, at 1:46 PM, Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org> wrote:
>
>
>
>> -----Original Message-----
>> From: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of Chuck Lever
>> Sent: Monday, February 08, 2016 11:26 AM
>> To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> Subject: [PATCH v2 9/9] svcrdma: Use new CQ API for RPC-over-RDMA server send CQs
>>
>> Calling ib_poll_cq() to sort through WCs during a completion is a
>> common pattern amongst RDMA consumers. Since commit 14d3a3b2498e
>> ("IB: add a proper completion queue abstraction"), WC sorting can
>> be handled by the IB core.
>>
>> By converting to this new API, svcrdma is made a better neighbor to
>> other RDMA consumers, as it allows the core to schedule the delivery
>> of completions more fairly amongst all active consumers.
>>
>> This new API also aims each completion at a function that is
>> specific to the WR's opcode. Thus the ctxt->wr_op field and the
>> switch in process_context is replaced by a set of methods that
>> handle each completion type.
>>
>> The server's rdma_stat_sq_poll and rdma_stat_sq_prod metrics are no
>> longer updated.
>>
>> As a clean up, the cq_event_handler, the dto_tasklet, and all
>> associated locking is removed, as they are no longer referenced or
>> used.
>>
>> Signed-off-by: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
>> ---
>
> <snip>
>
>> @@ -310,26 +311,26 @@ int rdma_read_chunk_frmr(struct svcxprt_rdma *xprt,
>>
>> /* Prepare RDMA_READ */
>> memset(&read_wr, 0, sizeof(read_wr));
>> + ctxt->cqe.done = svc_rdma_wc_read;
>> + read_wr.wr.wr_cqe = &ctxt->cqe;
>> read_wr.wr.send_flags = IB_SEND_SIGNALED;
>> read_wr.rkey = rs_handle;
>> read_wr.remote_addr = rs_offset;
>> read_wr.wr.sg_list = ctxt->sge;
>> read_wr.wr.num_sge = 1;
>> if (xprt->sc_dev_caps & SVCRDMA_DEVCAP_READ_W_INV) {
>> - read_wr.wr.opcode = IB_WR_RDMA_READ_WITH_INV;
>> - read_wr.wr.wr_id = (unsigned long)ctxt;
>> read_wr.wr.ex.invalidate_rkey = ctxt->frmr->mr->lkey;
>
> Hey Chuck, I found this bug by testing. You mistakenly removed setting the wr opcode for READ_WITH_INV above.
>
> This fixed it:
>
> @@ -319,6 +319,7 @@ int rdma_read_chunk_frmr(struct svcxprt_rdma *xprt,
> read_wr.wr.sg_list = ctxt->sge;
> read_wr.wr.num_sge = 1;
> if (xprt->sc_dev_caps & SVCRDMA_DEVCAP_READ_W_INV) {
> + read_wr.wr.opcode = IB_WR_RDMA_READ_WITH_INV;
> read_wr.wr.ex.invalidate_rkey = ctxt->frmr->mr->lkey;
> } else {
> read_wr.wr.opcode = IB_WR_RDMA_READ;
>
> And with this patch, it tests out over iWARP/cxgb4.
>
> Tested-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
I was attempting to remove all instances of ctxt->wr_op
and got overzealous. Thanks for the testing and bug report!
This fix will appear in the next version of the series.
--
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
prev parent reply other threads:[~2016-02-11 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 17:24 [PATCH v2 0/9] NFS/RDMA server patches for v4.6 Chuck Lever
[not found] ` <20160208171756.13423.14384.stgit-Hs+gFlyCn65vLzlybtyyYzGyq/o6K9yX@public.gmane.org>
2016-02-08 17:24 ` [PATCH v2 1/9] svcrdma: Do not send XDR roundup bytes for a write chunk Chuck Lever
[not found] ` <20160208172430.13423.18896.stgit-Hs+gFlyCn65vLzlybtyyYzGyq/o6K9yX@public.gmane.org>
2016-02-08 19:21 ` J. Bruce Fields
[not found] ` <20160208192119.GF17411-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2016-02-08 20:03 ` Chuck Lever
2016-02-08 17:24 ` [PATCH v2 2/9] svcrdma: svc_rdma_post_recv() should close connection on error Chuck Lever
2016-02-08 17:24 ` [PATCH v2 3/9] rpcrdma: Add RPCRDMA_HDRLEN_ERR Chuck Lever
2016-02-08 17:24 ` [PATCH v2 4/9] svcrdma: Make RDMA_ERROR messages work Chuck Lever
2016-02-08 17:25 ` [PATCH v2 5/9] svcrdma: Use correct XID in error replies Chuck Lever
2016-02-08 17:25 ` [PATCH v2 6/9] svcrdma: Hook up the logic to return ERR_CHUNK Chuck Lever
2016-02-08 17:25 ` [PATCH v2 7/9] svcrdma: Remove close_out exit path Chuck Lever
2016-02-08 17:25 ` [PATCH v2 8/9] svcrdma: Use new CQ API for RPC-over-RDMA server receive CQs Chuck Lever
2016-02-08 17:25 ` [PATCH v2 9/9] svcrdma: Use new CQ API for RPC-over-RDMA server send CQs Chuck Lever
[not found] ` <20160208172537.13423.97332.stgit-Hs+gFlyCn65vLzlybtyyYzGyq/o6K9yX@public.gmane.org>
2016-02-11 18:46 ` Steve Wise
2016-02-11 18:48 ` Chuck Lever [this message]
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=46CB2961-FCAC-4901-B66C-B7B6503ADDF3@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=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@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: 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