From: Chuck Lever <chuck.lever@oracle.com>
To: Anna.Schumaker@netapp.com
Cc: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v4 01/16] xprtrdma: Enable swap-on-NFS/RDMA
Date: Sat, 24 Oct 2015 17:26:29 -0400 [thread overview]
Message-ID: <20151024212629.4715.58465.stgit@manet.1015granger.net> (raw)
In-Reply-To: <20151024211707.4715.61650.stgit@manet.1015granger.net>
After adding a swapfile on an NFS/RDMA mount and removing the
normal swap partition, I was able to push the NFS client well
into swap without any issue.
I forgot to swapoff the NFS file before rebooting. This pinned
the NFS mount and the IB core and provider, causing shutdown to
hang. I think this is expected and safe behavior. Probably
shutdown scripts should "swapoff -a" before unmounting any
filesystems.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Sagi Grimberg <sagig@mellanox.com>
Tested-By: Devesh Sharma <devesh.sharma@avagotech.com>
---
net/sunrpc/xprtrdma/transport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/sunrpc/xprtrdma/transport.c b/net/sunrpc/xprtrdma/transport.c
index 41e452b..e9e5ed7 100644
--- a/net/sunrpc/xprtrdma/transport.c
+++ b/net/sunrpc/xprtrdma/transport.c
@@ -676,7 +676,7 @@ static void xprt_rdma_print_stats(struct rpc_xprt *xprt, struct seq_file *seq)
static int
xprt_rdma_enable_swap(struct rpc_xprt *xprt)
{
- return -EINVAL;
+ return 0;
}
static void
next prev parent reply other threads:[~2015-10-24 21:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 21:26 [PATCH v4 00/16] NFS/RDMA patches for merging into v4.4 Chuck Lever
2015-10-24 21:26 ` Chuck Lever [this message]
2015-10-24 21:26 ` [PATCH v4 02/16] xprtrdma: Re-arm after missed events Chuck Lever
2015-10-24 21:26 ` [PATCH v4 03/16] xprtrdma: Prevent loss of completion signals Chuck Lever
2015-10-24 21:26 ` [PATCH v4 04/16] xprtrdma: Refactor reply handler error handling Chuck Lever
2015-10-24 21:27 ` [PATCH v4 05/16] xprtrdma: Replace send and receive arrays Chuck Lever
2015-10-24 21:27 ` [PATCH v4 06/16] xprtrdma: Use workqueue to process RPC/RDMA replies Chuck Lever
2015-10-24 21:27 ` [PATCH v4 07/16] xprtrdma: Remove reply tasklet Chuck Lever
2015-10-24 21:27 ` [PATCH v4 08/16] xprtrdma: Saving IRQs no longer needed for rb_lock Chuck Lever
2015-10-24 21:27 ` [PATCH v4 09/16] SUNRPC: Abstract backchannel operations Chuck Lever
2015-10-24 21:27 ` [PATCH v4 10/16] xprtrdma: Pre-allocate backward rpc_rqst and send/receive buffers Chuck Lever
2015-10-24 21:27 ` [PATCH v4 11/16] xprtrdma: Pre-allocate Work Requests for backchannel Chuck Lever
2015-10-24 21:27 ` [PATCH v4 12/16] xprtrdma: Add support for sending backward direction RPC replies Chuck Lever
2015-10-24 21:28 ` [PATCH v4 13/16] xprtrdma: Handle incoming backward direction RPC calls Chuck Lever
2015-10-24 21:28 ` [PATCH v4 14/16] svcrdma: Add backward direction service for RPC/RDMA transport Chuck Lever
2015-10-24 21:28 ` [PATCH v4 15/16] SUNRPC: Remove the TCP-only restriction in bc_svc_process() Chuck Lever
2015-10-24 21:28 ` [PATCH v4 16/16] NFS: Enable client side NFSv4.1 backchannel to use other transports Chuck Lever
2015-11-02 20:43 ` Anna Schumaker
2015-11-02 21:16 ` Chuck Lever
2015-11-02 21:29 ` Anna Schumaker
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=20151024212629.4715.58465.stgit@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=Anna.Schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox