From: Mel Gorman <mgorman@suse.de>
To: Jerome Marchand <jmarchan@redhat.com>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Christoph Hellwig <hch@infradead.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] nfs: avoid swap-over-NFS deadlock
Date: Thu, 3 Sep 2015 15:01:17 +0100 [thread overview]
Message-ID: <20150903140117.GE25655@suse.de> (raw)
In-Reply-To: <55E5D0B6.10307@redhat.com>
On Tue, Sep 01, 2015 at 06:22:14PM +0200, Jerome Marchand wrote:
> > Thanks. Sorry for the long delay but I finally got back to the bug this
> > week. NFS can be modified to special case the swapfile but I was not happy
> > with the result for multiple reasons. It took me a while to see a way for
> > the core VM to deal with it. What do you think of the following
> > approach?
>
> Seems sound to me.
>
> > More importantly, does it work for you?
>
> Yes.
>
Sweet, thanks. It's the merge window now so it won't get fixed now and I
know there is already a collision with the mm merge. I'll rebase and
repost after 4.3-rc1 comes out.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2015-09-03 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 8:10 [RFC PATCH] nfs: avoid swap-over-NFS deadlock Jerome Marchand
2015-07-22 12:23 ` Trond Myklebust
2015-07-22 13:46 ` Jerome Marchand
2015-07-27 10:52 ` Mel Gorman
2015-07-27 11:25 ` Jerome Marchand
2015-08-20 12:23 ` Mel Gorman
2015-09-01 16:22 ` Jerome Marchand
2015-09-03 14:01 ` Mel Gorman [this message]
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=20150903140117.GE25655@suse.de \
--to=mgorman@suse.de \
--cc=anna.schumaker@netapp.com \
--cc=hch@infradead.org \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=trond.myklebust@primarydata.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;
as well as URLs for NNTP newsgroup(s).