From: Tom Tucker <tom@opengridcomputing.com>
To: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Cc: Neil Brown <neilb@suse.de>, Tom Talpey <Thomas.Talpey@netapp.com>,
Peter Leckie <pleckie@melbourne.sgi.com>,
Greg Banks <gnb@sgi.com>
Subject: [RFC,PATCH 7/15] knfsd: create RDMA transport in nfssvc
Date: Fri, 18 May 2007 12:45:31 -0500 [thread overview]
Message-ID: <1179510331.23385.120.camel@trinity.ogc.int> (raw)
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;
}
-------------------------------------------------------------------------
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 reply other threads:[~2007-05-18 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 17:45 Tom Tucker [this message]
2007-05-21 7:04 ` [RFC,PATCH 7/15] knfsd: create RDMA transport in nfssvc Neil Brown
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=1179510331.23385.120.camel@trinity.ogc.int \
--to=tom@opengridcomputing.com \
--cc=Thomas.Talpey@netapp.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