From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: thomas.talpey@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 00/12] svcrdma: Fast memory registration support
Date: Wed, 8 Oct 2008 18:26:47 -0400 [thread overview]
Message-ID: <20081008222647.GE14527@fieldses.org> (raw)
In-Reply-To: <1223069629-5267-1-git-send-email-tom@opengridcomputing.com>
On Fri, Oct 03, 2008 at 04:33:37PM -0500, Tom Tucker wrote:
>
> Bruce:
>
> This updated patchset implements support for Fast Memory Registration
> in the NFS server. The second to last patch has been updated to
> provide better guidance on whether the connection is safe or
> not. Basically the code gives you a qualification string instead of
> expecting the administrator to know how to interpret the memory
> registration strategy and transport idiosyncrasies. The documentation
> has also been updated given your suggestions and the change to the
> informative log message. The string is certainly informative, but may
> be a little long. For this reason, there is a proc file entry to
> disable it.
OK, thanks, I've applied the first 10 patches (actually, merged them
from the for-bfields branch of your git tree).
I'm still a little iffy on patch #11.
--b.
>
> Fast Memory Regstration is the ability to quickly map a kernel memory
> page list as a logically contiguous memory region from the perspective
> of the adapter. This mapping is created and invalidated using work
> requests posted on the SQ.
>
> There are two benefits of this new memory registration strategy:
>
> - It allows for large amounts of data to be transferred between the
> client and server with a single work request
>
> - It improves security since the effective lifetime and scope of an
> RKEY is a single RPC and WR.
>
> The documentation file Documentation/filesystems/nfs-rdma.txt file has
> been updated with information about NFSRDMA security in general and
> how it is affected by the new Fast Memory Registration capability.
>
> This new capability is only enabled if the underlying device advertises
> that it is supported. It is not necessary that both the client and
> server use the same strategy, however, for Fast Memory Registration,
> it improves performance.
>
> These patches are also available here:
> git://git.linux-nfs.org/projects/tomtucker/xprt-switch-2.6.git
>
> Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
>
>
> [PATCH 01/12] svcrdma: Add Fast Reg MR Data Types
>
> include/linux/sunrpc/svc_rdma.h | 22 +++++++++++++++++++++-
> 1 files changed, 21 insertions(+), 1 deletions(-)
>
> [PATCH 02/12] svcrdma: Add FRMR get/put services
>
> include/linux/sunrpc/svc_rdma.h | 3 +
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 122 ++++++++++++++++++++++++++++-
> 2 files changed, 120 insertions(+), 5 deletions(-)
>
> [PATCH 03/12] svcrdma: Query device for Fast Reg support during connection setup
>
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 76 +++++++++++++++++++++++++++--
> 1 files changed, 70 insertions(+), 6 deletions(-)
>
> [PATCH 04/12] svcrdma: Add a service to register a Fast Reg MR with the device
>
> include/linux/sunrpc/svc_rdma.h | 1 +
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 118 +++++++++++++++++++++---------
> 2 files changed, 84 insertions(+), 35 deletions(-)
>
> [PATCH 05/12] svcrdma: Modify post recv path to use local dma key
>
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 12 +++++++++---
> 1 files changed, 9 insertions(+), 3 deletions(-)
>
> [PATCH 06/12] svcrdma: Add support to svc_rdma_send to handle chained WR
>
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 29 +++++++++++++++++++++--------
> 1 files changed, 21 insertions(+), 8 deletions(-)
>
> [PATCH 07/12] svcrdma: Modify the RPC recv path to use FRMR when available
>
> include/linux/sunrpc/svc_rdma.h | 1 +
> net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 187 ++++++++++++++++++++++++++----
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 5 +-
> 3 files changed, 171 insertions(+), 22 deletions(-)
>
> [PATCH 08/12] svcrdma: Modify the RPC reply path to use FRMR when available
>
> net/sunrpc/xprtrdma/svc_rdma_sendto.c | 263 +++++++++++++++++++++++++-----
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 2 +
> 2 files changed, 225 insertions(+), 40 deletions(-)
>
> [PATCH 09/12] svcrdma: Update svc_rdma_send_error to use DMA LKEY
>
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 11 +++++++++--
> 1 files changed, 9 insertions(+), 2 deletions(-)
>
> [PATCH 10/12] svcrdma: Fix IRD/ORD polarity
>
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> [PATCH 11/12] svcrdma: Add a message log string to indicate if FastReg is being used
>
> include/linux/sunrpc/svc_rdma.h | 1 +
> net/sunrpc/xprtrdma/svc_rdma.c | 8 ++++
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 63 ++++++++++++++++++-----------
> 3 files changed, 48 insertions(+), 24 deletions(-)
>
> [PATCH 12/12] svcrdma: Documentation update for the FastReg memory model
>
> Documentation/filesystems/nfs-rdma.txt | 126 ++++++++++++++++++++++++++++++++
> 1 files changed, 126 insertions(+), 0 deletions(-)
>
prev parent reply other threads:[~2008-10-08 22:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 21:33 [PATCH 00/12] svcrdma: Fast memory registration support Tom Tucker
2008-10-03 21:33 ` [PATCH 01/12] svcrdma: Add Fast Reg MR Data Types Tom Tucker
2008-10-03 21:33 ` [PATCH 02/12] svcrdma: Add FRMR get/put services Tom Tucker
2008-10-03 21:33 ` [PATCH 03/12] svcrdma: Query device for Fast Reg support during connection setup Tom Tucker
2008-10-03 21:33 ` [PATCH 04/12] svcrdma: Add a service to register a Fast Reg MR with the device Tom Tucker
2008-10-03 21:33 ` [PATCH 05/12] svcrdma: Modify post recv path to use local dma key Tom Tucker
2008-10-03 21:33 ` [PATCH 06/12] svcrdma: Add support to svc_rdma_send to handle chained WR Tom Tucker
2008-10-03 21:33 ` [PATCH 07/12] svcrdma: Modify the RPC recv path to use FRMR when available Tom Tucker
2008-10-03 21:33 ` [PATCH 08/12] svcrdma: Modify the RPC reply " Tom Tucker
2008-10-03 21:33 ` [PATCH 09/12] svcrdma: Update svc_rdma_send_error to use DMA LKEY Tom Tucker
2008-10-03 21:33 ` [PATCH 10/12] svcrdma: Fix IRD/ORD polarity Tom Tucker
2008-10-03 21:33 ` [PATCH 11/12] svcrdma: Add a message log string to indicate if FastReg is being used Tom Tucker
2008-10-03 21:33 ` [PATCH 12/12] svcrdma: Documentation update for the FastReg memory model Tom Tucker
2008-10-08 22:48 ` [PATCH 11/12] svcrdma: Add a message log string to indicate if FastReg is being used J. Bruce Fields
2008-10-09 6:37 ` Tom Tucker
2008-10-09 16:26 ` J. Bruce Fields
2008-10-09 18:46 ` Tom Tucker
2008-10-10 21:02 ` J. Bruce Fields
2008-10-13 2:18 ` Tom Tucker
2008-10-13 2:20 ` Tom Tucker
2008-10-22 20:23 ` J. Bruce Fields
2008-10-22 21:37 ` Tom Tucker
2008-10-04 1:05 ` [PATCH 02/12] svcrdma: Add FRMR get/put services Tom Tucker
2008-10-06 20:02 ` Tom Tucker
2008-10-08 22:26 ` 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=20081008222647.GE14527@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=thomas.talpey@netapp.com \
--cc=tom@opengridcomputing.com \
/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.