From: Neil Brown <neilb@suse.de>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: 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 7/15] knfsd: create RDMA transport in nfssvc
Date: Mon, 21 May 2007 17:04:40 +1000 [thread overview]
Message-ID: <18001.17544.798341.277657@notabene.brown> (raw)
In-Reply-To: message from Tom Tucker on Friday May 18
On Friday May 18, tom@opengridcomputing.com wrote:
> Adds a call to the svc_makesock routine to create the RDMA transport.
> I think this should somehow be linked to the transport switch and the
> port mapper.
>
> Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
> ---
>
> fs/nfsd/nfssvc.c | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
> index d7759ce..4a7982e 100644
> --- a/fs/nfsd/nfssvc.c
> +++ b/fs/nfsd/nfssvc.c
> @@ -254,6 +254,17 @@ #ifdef CONFIG_NFSD_TCP
> if (error < 0)
> return error;
> #endif
> +#ifdef CONFIG_NFSD_RDMA
> + /* KLUDGE: The rpc.nfsd utility passes down the
> + * port number when it opens the nfsd file. We are
> + * going to ignore it here and force the RDMA port number
> + * to 2050. This will allow the TCP transport to coexist
> + * with the RDMA transport.
> + */
> + error = svc_makesock(nfsd_serv, IPPROTO_MAX, 2050 /* port */, 0);
> + if (error < 0)
> + return error;
> +#endif
> return 0;
> }
>
As you say: KLUDGE.
What is really going on here? Why don't we have a protocol number,
and why can't we use port 2049?
I don't know a lot about RDMA (feel free to educate me) but it seems
that there is some connection to IP (is this IPoIB??) in that IP
address seem to be available for the end points.
Can you distinguish an RDMA connection from any other IP connection
simply based on the interface it gets routed through?
Can you actually get any sort of socket representing an RDMA
connection? I appreciate that normal sendmsg/recvmsg calls on the
socket aren't going to work, but I'm dreaming that maybe a
socket-level 'accept' could establish the connection. Then we look at
the connection, discover it is on a RDMA-capable device, and start
using the RDMA interface to move data around.
Does that make any sense at all, or am I totally off-beam?
NeilBrown
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-05-21 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 17:45 [RFC,PATCH 7/15] knfsd: create RDMA transport in nfssvc Tom Tucker
2007-05-21 7:04 ` Neil Brown [this message]
2007-05-21 15:49 ` Tom Tucker
2007-05-22 6:21 ` Neil Brown
2007-05-22 15:59 ` Tom Tucker
2007-05-23 15:00 ` Talpey, Thomas
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=18001.17544.798341.277657@notabene.brown \
--to=neilb@suse.de \
--cc=Thomas.Talpey@netapp.com \
--cc=gnb@sgi.com \
--cc=nfs@lists.sourceforge.net \
--cc=pleckie@melbourne.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox