From: Tom Tucker <tom@opengridcomputing.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: [RFC,PATCH 7/8] rdma: makefile
Date: Mon, 03 Dec 2007 11:26:19 -0600 [thread overview]
Message-ID: <1196702779.5811.3.camel@trinity.ogc.int> (raw)
In-Reply-To: <2F4C0A61-33B5-4D2D-9349-657EC856A8B2@oracle.com>
On Mon, 2007-12-03 at 12:00 -0500, Chuck Lever wrote:
> On Nov 29, 2007, at 5:45 PM, Tom Tucker wrote:
> > Add the NFSD_RDMA module to the sunrpc makefile.
>
> General question about how the RPC level RDMA code is organized: The
> client-side RDMA service provider lives in its own subdirectory of
> net/sunrpc. Should the server side provider also live in that
> directory? Should these two be glued together into a single module?
>
I don't think so because the client and server are truly independent and
of course, you will often mount over RDMA, but not serve over RDMA.
What's the fan-out 20-1?
> > Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
> > ---
> >
> > net/sunrpc/Makefile | 4 ++++
> > 1 files changed, 4 insertions(+), 0 deletions(-)
> >
> > diff --git a/net/sunrpc/Makefile b/net/sunrpc/Makefile
> > index 92e1dbe..6d03dbf 100644
> > --- a/net/sunrpc/Makefile
> > +++ b/net/sunrpc/Makefile
> > @@ -15,3 +15,7 @@ sunrpc-y := clnt.o xprt.o socklib.o xprtsock.o
> > sched.o \
> > svc_xprt.o
> > sunrpc-$(CONFIG_PROC_FS) += stats.o
> > sunrpc-$(CONFIG_SYSCTL) += sysctl.o
> > +
> > +obj-$(CONFIG_NFSD_RDMA) += svcrdma.o
> > +svcrdma-y := svc_rdma.o svc_rdma_transport.o \
> > + svc_rdma_marshal.o svc_rdma_sendto.o svc_rdma_recvfrom.o
>
>
> --
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
> -
> 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:[~2007-12-03 17:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 22:44 [RFC,PATCH 0/8] RDMA Transport Provider Tom Tucker
[not found] ` <20071129224412.14887.14136.stgit-gUwIgmpLGaKNDNWfRnPdfg@public.gmane.org>
2007-11-29 22:45 ` [RFC,PATCH 1/8] rdma: SVCRMDA Header File Tom Tucker
2007-11-29 22:45 ` [RFC,PATCH 2/8] rdma: SVCRDMA Transport Module Tom Tucker
2007-11-29 22:45 ` [RFC,PATCH 3/8] rdma: SVCRDMA Core Transport Services Tom Tucker
2007-11-29 22:45 ` [RFC,PATCH 4/8] rdma: SVCRDMA recvfrom Tom Tucker
2007-11-29 22:45 ` [RFC,PATCH 5/8] rdma: SVCRDMA sendto Tom Tucker
2007-11-29 22:45 ` [RFC,PATCH 6/8] rdma: ONCRPC RDMA protocol marshalling Tom Tucker
2007-11-29 22:45 ` [RFC,PATCH 7/8] rdma: makefile Tom Tucker
[not found] ` <20071129224513.14887.8074.stgit-gUwIgmpLGaKNDNWfRnPdfg@public.gmane.org>
2007-12-03 17:00 ` Chuck Lever
2007-12-03 17:24 ` Tom Tucker
[not found] ` <1196702699.5811.0.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2007-12-03 17:25 ` J. Bruce Fields
2007-12-03 17:26 ` Tom Tucker [this message]
2007-12-03 17:08 ` [RFC,PATCH 7/8] rdma: makefile (second thread) Chuck Lever
2007-12-03 20:29 ` James Lentini
[not found] ` <Pine.LNX.4.64.0712031524250.7142-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2007-12-03 20:52 ` Chuck Lever
2007-12-03 22:29 ` James Lentini
[not found] ` <Pine.LNX.4.64.0712031656150.7142-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2007-12-04 0:52 ` Chuck Lever
2007-12-04 23:04 ` James Lentini
[not found] ` <Pine.LNX.4.64.0712041800270.7142-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2007-12-05 3:08 ` Chuck Lever
2007-11-29 22:45 ` [RFC,PATCH 8/8] rdma: Kconfig Tom Tucker
2007-11-30 4:45 ` [RFC,PATCH 0/8] RDMA Transport Provider J. Bruce Fields
2007-11-30 15:59 ` Tom Tucker
[not found] ` <1196438368.5432.10.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2007-11-30 17:16 ` J. Bruce Fields
2007-11-30 19:41 ` Tom Tucker
[not found] ` <1196451693.5432.35.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2007-11-30 20:48 ` Chuck Lever
2007-11-30 20:50 ` 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=1196702779.5811.3.camel@trinity.ogc.int \
--to=tom@opengridcomputing.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--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.