From: Tom Tucker <tom@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 02/11] svcrdma: Use RPC reply map for RDMA_WRITE processing
Date: Mon, 23 Jun 2008 21:29:57 -0500 [thread overview]
Message-ID: <48605C25.4000503@opengridcomputing.com> (raw)
In-Reply-To: <20080623182114.GB24373@fieldses.org>
J. Bruce Fields wrote:
> On Sat, Jun 21, 2008 at 11:26:52AM -0500, Tom Tucker wrote:
>
>> J. Bruce Fields wrote:
>>
>>> Also, the only caller of xdr_to_sge() appears to be svc_rdma_sendto(),
>>> which is called from svc_sendto() immediately after setting:
>>>
>>> xb = &rqstp->rq_res;
>>> xb->len = xb->head[0].iov_len + xb->page_len +
>>> xb->tail[0].iov_len;
>>>
>>> So I think xdr_to_sge() is doing a bunch of unnecessary work to handle
>>> the case where xdr->len could be less than that sum?
>>>
>>>
>>>
>> Ok... check me below please.
>>
>>>> /* Head SGE */
>>>> - sge[sge_no].addr = ib_dma_map_single(xprt->sc_cm_id->device,
>>>> - xdr->head[0].iov_base,
>>>> - xdr->head[0].iov_len,
>>>> - DMA_TO_DEVICE);
>>>> + vec->sge[sge_no].iov_base = xdr->head[0].iov_base;
>>>> sge_bytes = min_t(u32, byte_count, xdr->head[0].iov_len);
>>>>
>>>>
>> This doesn't need to be min_t. It could be xdr->head[0].iov_len.
>>
>
> Yes. The variable byte_count shouldn't be needed at all, so I'd start
> by eliminating all references to byte_count.
>
>
>>>> byte_count -= sge_bytes;
>>>> - sge[sge_no].length = sge_bytes;
>>>> - sge[sge_no].lkey = xprt->sc_phys_mr->lkey;
>>>> + vec->sge[sge_no].iov_len = sge_bytes;
>>>> sge_no++;
>>>> /* pages SGE */
>>>> @@ -99,16 +94,13 @@ static struct ib_sge *xdr_to_sge(struct svcxprt_rdma *xprt,
>>>> page_bytes = xdr->page_len;
>>>> page_off = xdr->page_base;
>>>> while (byte_count && page_bytes) {
>>>> + vec->sge[sge_no].iov_base =
>>>> + page_address(xdr->pages[page_no]) + page_off;
>>>> sge_bytes = min_t(u32, byte_count, (PAGE_SIZE-page_off));
>>>>
>>>>
>> This is still needed if the xdr terminates with a portion of a page and
>> there is not tail.
>>
>
> Yes, but the condition could just be (page_bytes).
>
>
Right.
>>>> - sge[sge_no].addr =
>>>> - ib_dma_map_page(xprt->sc_cm_id->device,
>>>> - xdr->pages[page_no], page_off,
>>>> - sge_bytes, DMA_TO_DEVICE);
>>>> sge_bytes = min(sge_bytes, page_bytes);
>>>> byte_count -= sge_bytes;
>>>> page_bytes -= sge_bytes;
>>>> - sge[sge_no].length = sge_bytes;
>>>> - sge[sge_no].lkey = xprt->sc_phys_mr->lkey;
>>>> + vec->sge[sge_no].iov_len = sge_bytes;
>>>> sge_no++;
>>>> page_no++;
>>>> @@ -117,23 +109,17 @@ static struct ib_sge *xdr_to_sge(struct svcxprt_rdma *xprt,
>>>> /* Tail SGE */
>>>> if (byte_count && xdr->tail[0].iov_len) {
>>>>
>>>>
>> This is defensive. It could just be byte_count.
>>
>
> I agree, though I'd just make it (xdr->tail[0].iov_len) instead of just
> (byte_count).
>
>
Agreed.
>> If byte_count != xdr->tail[0].iov_len, the BUG_ON below will let us know.
>>
>>>> - sge[sge_no].addr =
>>>> - ib_dma_map_single(xprt->sc_cm_id->device,
>>>> - xdr->tail[0].iov_base,
>>>> - xdr->tail[0].iov_len,
>>>> - DMA_TO_DEVICE);
>>>> + vec->sge[sge_no].iov_base = xdr->tail[0].iov_base;
>>>> sge_bytes = min_t(u32, byte_count, xdr->tail[0].iov_len);
>>>>
>>>>
>> The min_t isn't needed. It could just be byte_count.
>>
>
> Right, but could also just be tail length, as above.
>
>
Ok, page # confirmed...
> --b.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-06-24 2:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12120836962076-git-send-email-tom@opengridcomputing.com>
2008-05-29 22:10 ` [PATCH 0/11] svcrdma: WR context management bug fixes and cleanup J. Bruce Fields
2008-05-29 22:25 ` Tom Tucker
[not found] ` <1212099937.22478.3.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2008-05-29 22:26 ` Roland Dreier
[not found] ` <12120836962324-git-send-email-tom@opengridcomputing.com>
2008-06-16 19:48 ` [PATCH 01/11] svcrdma: Add a type for keeping NFS RPC mapping J. Bruce Fields
2008-06-21 16:31 ` Tom Tucker
2008-06-23 18:27 ` J. Bruce Fields
2008-06-24 2:58 ` Tom Tucker
2008-06-24 19:58 ` J. Bruce Fields
2008-06-24 20:31 ` Benny Halevy
2008-06-24 20:38 ` Trond Myklebust
[not found] ` <12120836963727-git-send-email-tom@opengridcomputing.com>
2008-06-16 21:04 ` [PATCH 02/11] svcrdma: Use RPC reply map for RDMA_WRITE processing J. Bruce Fields
2008-06-21 16:26 ` Tom Tucker
2008-06-23 18:21 ` J. Bruce Fields
2008-06-24 2:29 ` Tom Tucker [this message]
2008-06-21 16:51 ` Tom Tucker
2008-06-23 18:51 ` J. Bruce Fields
2008-06-24 3:02 ` Tom Tucker
[not found] ` <1212083697950-git-send-email-tom@opengridcomputing.com>
[not found] ` <1212083697236-git-send-email-tom@opengridcomputing.com>
[not found] ` <12120836973390-git-send-email-tom@opengridcomputing.com>
[not found] ` <12120836973638-git-send-email-tom@opengridcomputing.com>
[not found] ` <12120836973072-git-send-email-tom@opengridcomputing.com>
[not found] ` <12120836972503-git-send-email-tom@opengridcomputing.com>
[not found] ` <12120836973166-git-send-email-tom@opengridcomputing.com>
[not found] ` <12120836972648-git-send-email-tom@opengridcomputing.com>
2008-06-16 21:24 ` [PATCH 10/11] svcrdma: Create a kmem cache for the WR contexts J. Bruce Fields
2008-06-21 17:08 ` Tom Tucker
2008-07-03 2:27 [PATCH 00/11] svcrdma: WR context management bug fixes and cleanup Tom Tucker
2008-07-03 2:27 ` [PATCH 01/11] svcrdma: Add a type for keeping NFS RPC mapping Tom Tucker
2008-07-03 2:27 ` [PATCH 02/11] svcrdma: Use RPC reply map for RDMA_WRITE processing Tom Tucker
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=48605C25.4000503@opengridcomputing.com \
--to=tom@opengridcomputing.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@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.