linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tom Tucker <tom@ogc.us>
Cc: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH 0/2] svcrdma: NFSRDMA Server fixes for 2.6.37
Date: Tue, 19 Oct 2010 10:54:43 -0400	[thread overview]
Message-ID: <20101019145443.GA16742@fieldses.org> (raw)
In-Reply-To: <20101012203332.22154.37230.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>

On Tue, Oct 12, 2010 at 03:33:46PM -0500, Tom Tucker wrote:
> Hi Bruce,
> 
> These fixes are ready for 2.6.37. They fix two bugs in the server-side
> NFSRDMA transport.

Both applied and pushed out, thanks.

--b.

> 
> Thanks,
> Tom
> ---
> 
> Tom Tucker (2):
>       svcrdma: Cleanup DMA unmapping in error paths.
>       svcrdma: Change DMA mapping logic to avoid the page_address kernel API
> 
> 
>  net/sunrpc/xprtrdma/svc_rdma_recvfrom.c  |   19 ++++---
>  net/sunrpc/xprtrdma/svc_rdma_sendto.c    |   82 ++++++++++++++++++++++--------
>  net/sunrpc/xprtrdma/svc_rdma_transport.c |   41 +++++++--------
>  3 files changed, 92 insertions(+), 50 deletions(-)
> 
> -- 
> Signed-off-by: Tom Tucker <tom@ogc.us>

      parent reply	other threads:[~2010-10-19 14:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 20:33 [PATCH 0/2] svcrdma: NFSRDMA Server fixes for 2.6.37 Tom Tucker
2010-10-12 20:33 ` [PATCH 1/2] svcrdma: Change DMA mapping logic to avoid the page_address kernel API Tom Tucker
2010-11-16 19:39   ` Or Gerlitz
2010-11-18  5:26     ` Tom Tucker
2010-10-12 20:33 ` [PATCH 2/2] svcrdma: Cleanup DMA unmapping in error paths Tom Tucker
     [not found] ` <20101012203332.22154.37230.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2010-10-19 14:54   ` J. Bruce Fields [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=20101019145443.GA16742@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=tom@ogc.us \
    /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;
as well as URLs for NNTP newsgroup(s).