From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Christoph Hellwig <hch@lst.de>, Miaohe Lin <linmiaohe@huawei.com>,
linux-nfs@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Finalising swap-over-NFS patches
Date: Fri, 29 Apr 2022 10:43:34 +1000 [thread overview]
Message-ID: <165119280115.15698.2629172320052218921.stgit@noble.brown> (raw)
Hi Andrew,
Two patches for current -mm branch.
First fixes an omission pointed out by Miaohe Lin. Huge pages weren't
handled correctly.
Second changes NFS to use the new ->swap_rw
With this, swap over NFS largely works again. I think there is a little
more work to do in NFS/SUNRPC code to make allocations on the swap out
path behave optimally. Any such changes can go through the NFS tree.
Thanks,
NeilBrown
---
NeilBrown (2):
MM: handle THP in swap_*page_fs()
NFS: rename nfs_direct_IO and use as ->swap_rw
fs/nfs/direct.c | 23 ++++++++++-------------
fs/nfs/file.c | 5 +----
include/linux/nfs_fs.h | 2 +-
mm/page_io.c | 23 +++++++++++++----------
4 files changed, 25 insertions(+), 28 deletions(-)
--
Signature
next reply other threads:[~2022-04-29 0:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 0:43 NeilBrown [this message]
2022-04-29 0:43 ` [PATCH 1/2] MM: handle THP in swap_*page_fs() NeilBrown
2022-04-29 1:21 ` Andrew Morton
2022-04-29 1:57 ` NeilBrown
2022-04-29 8:13 ` Miaohe Lin
2022-04-29 19:04 ` Yang Shi
2022-05-02 4:23 ` NeilBrown
2022-05-02 17:48 ` Yang Shi
2022-05-04 23:41 ` NeilBrown
2022-05-06 2:56 ` ying.huang
2022-04-29 0:43 ` [PATCH 2/2] NFS: rename nfs_direct_IO and use as ->swap_rw NeilBrown
2022-04-29 1:23 ` Andrew Morton
2022-04-29 2:05 ` NeilBrown
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=165119280115.15698.2629172320052218921.stgit@noble.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=geert+renesas@glider.be \
--cc=hch@lst.de \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).