Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
From:   "NeilBrown" <neilb@suse.de>
To:     "Trond Myklebust" <trond.myklebust@hammerspace.com>,
        "Anna Schumaker" <anna@kernel.org>
Cc:     linux-nfs@vger.kernel.org
Subject: Re: [PATCH 00/11] Various NFS/sunrpc improvements for swap-over-NFS
In-reply-to: <164660993703.31054.17075972410545449555.stgit@noble.brown>
References: <164660993703.31054.17075972410545449555.stgit@noble.brown>
Date:   Thu, 10 Mar 2022 11:48:09 +1100
Message-id: <164687328986.31932.14664341490828467390@noble.neil.brown.name>
Precedence: bulk

On Mon, 07 Mar 2022, NeilBrown wrote:
> swap-over-NFS currently doesn't work.  Even after these patches it still
> won't work.  Some core MM changes are needed.
> However these patches make a number of improvements to NFS and SUNRPC so
> that swap-over-NFS can work once those mm changes land.
> 
> There is one change since the last posting of these patches.
> The last patch was added to fix a potential hang when enabling swap.
> 
> Trond/Anna - is their any chance these can go in on the next merge
> window?
> 
> Thanks,
> NeilBrown
> 
> 
> ---
> 
> NeilBrown (11):
>       NFS: remove IS_SWAPFILE hack
>       SUNRPC/call_alloc: async tasks mustn't block waiting for memory
>       SUNRPC/auth: async tasks mustn't block waiting for memory
>       SUNRPC/xprt: async tasks mustn't block waiting for memory

I note that the above two have minor conflcts when applied to linux-next
due to some GFP_NOFS having been changed to GFP_KERNEL.  Would you like
me to resend thee two?  Or resend the series?  Or are you happy to just
if it up?

Thanks,
NeilBrown