Linux NFS development
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: nfs@lists.sourceforge.net
Cc: bfields@fieldses.org, neilb@suse.de, gnb@sgi.com
Subject: [RFC,PATCH 10/10] rdma: Kconfig
Date: Fri, 19 Oct 2007 16:56:30 -0500	[thread overview]
Message-ID: <20071019215630.31937.8096.stgit@dell3.ogc.int> (raw)
In-Reply-To: <20071019215304.31937.28876.stgit@dell3.ogc.int>


Add NFS_RDMA as an option to the Kconfig file.

Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
---

 fs/Kconfig |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/fs/Kconfig b/fs/Kconfig
index f9eed6d..b5d67f4 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -1649,6 +1649,13 @@ config NFSD
 	  To compile the NFS server support as a module, choose M here: the
 	  module will be called nfsd.  If unsure, say N.
 
+config NFSD_RDMA
+	tristate "Provide NFS server over RDMA support (EXPERIMENTAL)"
+	depends on SUNRPC && NFSD && INFINIBAND && EXPERIMENTAL
+	help
+	  If you want your NFS server to support RDMA connections, 
+	  say M or Y here. If unsure, say N.
+
 config NFSD_V2_ACL
 	bool
 	depends on NFSD

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2007-10-19 21:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 21:53 [RFC,PATCH 00/10] rdma: SVCRDMA Transport Driver Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 01/10] rdma: ONCRPC RDMA Header File Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 02/10] rdma: sysctl for SVCRDMA transport module Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 03/10] rdma: SVCRMDA Header File Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 04/10] rdma: SVCRDMA Transport Module Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 05/10] rdma: SVCRDMA Core Transport Services Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 06/10] rdma: SVCRDMA recvfrom Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 07/10] rdma: SVCRDMA sendto Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 08/10] rdma: ONCRPC RDMA protocol marshalling Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 09/10] rdma: makefile Tom Tucker
2007-10-19 21:56 ` Tom Tucker [this message]
2007-10-22 22:02 ` [RFC,PATCH 00/10] rdma: SVCRDMA Transport Driver J. Bruce Fields
2007-10-22 22:03   ` J. Bruce Fields
2007-10-23  2:44   ` Tom Tucker
2007-10-23 18:05     ` J. Bruce Fields
     [not found] <20070820165635.15938.57184.stgit@dell3.ogc.int>
2007-08-20 16:58 ` [RFC,PATCH 10/10] rdma: Kconfig Tom Tucker
  -- strict thread matches above, loose matches on Subject: below --
2007-07-01 23:02 [RFC,PATCH 00/10] knfsd: RMDA Transport Driver v2 Tom Tucker
2007-07-01 23:12 ` [RFC,PATCH 10/10] rdma: Kconfig Tom Tucker
2007-07-10 15:04   ` James Lentini
2007-07-11  4:11     ` 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=20071019215630.31937.8096.stgit@dell3.ogc.int \
    --to=tom@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=gnb@sgi.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /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