From: Tom Tucker <tom@opengridcomputing.com>
To: chuck.lever@oracle.com
Cc: Neil Brown <neilb@suse.de>, Tom Talpey <Thomas.Talpey@netapp.com>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Peter Leckie <pleckie@melbourne.sgi.com>,
Greg Banks <gnb@sgi.com>
Subject: Re: [RFC, PATCH 3/15] knfsd: initialize RDMA transport in sunrpc
Date: Fri, 18 May 2007 14:25:50 -0500 [thread overview]
Message-ID: <1179516350.23385.165.camel@trinity.ogc.int> (raw)
In-Reply-To: <464DF9E0.3050104@oracle.com>
On Fri, 2007-05-18 at 15:09 -0400, Chuck Lever wrote:
> As part of the client side transport switch, I constructed a transport
> "register" and "unregister" interface so that when a transport module is
> loaded, it's init routine is invoked automatically, and likewise when it
> is unloaded its cleanup routine is automatically invoked.
>
> I'd like to see the same here. I don't think we want to create a
> situation where you have to make source code changes in order to add new
> transport capabilities. Especially the distributors would be allergic
> to such a constraint.
>
> Please consider this change while going about the process of integrating
> the server-side transport switch with your RDMA transport.
Agreed.
>
> Tom Tucker wrote:
> > Add calls to the svc_rdma initialization and cleanup routines to the
> > sunrpc module init logic.
> >
> > Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
> > ---
> >
> > net/sunrpc/sunrpc_syms.c | 10 +++++++++-
> > 1 files changed, 9 insertions(+), 1 deletions(-)
> >
> > diff --git a/net/sunrpc/sunrpc_syms.c b/net/sunrpc/sunrpc_syms.c
> > index 43ecf62..16a50c9 100644
> > --- a/net/sunrpc/sunrpc_syms.c
> > +++ b/net/sunrpc/sunrpc_syms.c
> > @@ -20,7 +20,9 @@ #include <linux/sunrpc/svcsock.h>
> > #include <linux/sunrpc/auth.h>
> > #include <linux/workqueue.h>
> > #include <linux/sunrpc/rpc_pipe_fs.h>
> > -
> > +#ifdef CONFIG_NFSD_RDMA
> > +#include <linux/sunrpc/svc_rdma.h>
> > +#endif
> >
> > /* RPC scheduler */
> > EXPORT_SYMBOL(rpc_execute);
> > @@ -158,6 +160,9 @@ #endif
> > cache_register(&ip_map_cache);
> > cache_register(&unix_gid_cache);
> > init_socket_xprt();
> > +#ifdef CONFIG_NFSD_RDMA
> > + err = svc_rdma_init();
> > +#endif
> > out:
> > return err;
> > }
> > @@ -175,6 +180,9 @@ cleanup_sunrpc(void)
> > #ifdef RPC_DEBUG
> > rpc_unregister_sysctl();
> > #endif
> > +#ifdef CONFIG_NFSD_RDMA
> > + svc_rdma_cleanup();
> > +#endif
> > #ifdef CONFIG_PROC_FS
> > rpc_proc_exit();
> > #endif
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > NFS maillist - NFS@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-05-18 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 17:44 [RFC,PATCH 3/15] knfsd: initialize RDMA transport in sunrpc Tom Tucker
2007-05-18 18:23 ` [RFC, PATCH " Trond Myklebust
2007-05-18 18:54 ` Tom Tucker
2007-05-18 19:09 ` Chuck Lever
2007-05-18 19:25 ` Tom Tucker [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=1179516350.23385.165.camel@trinity.ogc.int \
--to=tom@opengridcomputing.com \
--cc=Thomas.Talpey@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=gnb@sgi.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=pleckie@melbourne.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox