From: "NeilBrown" <neilb@suse.de>
To: "David Howells" <dhowells@redhat.com>
Cc: dhowells@redhat.com, "Andrew Morton" <akpm@linux-foundation.org>,
"Christoph Hellwig" <hch@infradead.org>,
linux-nfs@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] MM changes to improve swap-over-NFS support
Date: Thu, 31 Mar 2022 12:12:41 +1100 [thread overview]
Message-ID: <164868916197.25542.11845352976146070176@noble.neil.brown.name> (raw)
In-Reply-To: <2923577.1648635976@warthog.procyon.org.uk>
On Wed, 30 Mar 2022, David Howells wrote:
> Do you have a branch with your patches on?
http://git.neil.brown.name/?p=linux.git;a=shortlog;h=refs/heads/swap-nfs
git://neil.brown.name/linux branch swap-nfs
Also on https://github.com/neilbrown/linux.git same branch
(it seems 1GB is no longer enough to run a git server for the kernel
effectively)
This contains
- recent HEAD from Linus, which includes the NFS work
- the patches I sent to akpm
- the patch to switch NFS over to using the new swap_rw
- a SUNRPC patch to fix an easy crash. But has always been there,
but recent changes to how kmalloc is called makes it much easier to
trigger.
NeilBrown
next prev parent reply other threads:[~2022-03-31 1:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 23:49 NeilBrown
2022-03-29 23:49 ` [PATCH 09/10] MM: submit multipage write for SWP_FS_OPS swap-space NeilBrown
2022-04-18 6:59 ` Miaohe Lin
2022-04-26 1:58 ` NeilBrown
2022-03-29 23:49 ` [PATCH 02/10] MM: drop swap_dirty_folio NeilBrown
2022-03-29 23:49 ` [PATCH 06/10] MM: perform async writes to SWP_FS_OPS swap-space using ->swap_rw NeilBrown
2022-03-29 23:49 ` [PATCH 07/10] DOC: update documentation for swap_activate and swap_rw NeilBrown
2022-03-29 23:49 ` [PATCH 08/10] MM: submit multipage reads for SWP_FS_OPS swap-space NeilBrown
2022-03-29 23:49 ` [PATCH 01/10] MM: create new mm/swap.h header file NeilBrown
2022-03-29 23:49 ` [PATCH 04/10] MM: reclaim mustn't enter FS for SWP_FS_OPS swap-space NeilBrown
2022-03-29 23:49 ` [PATCH 03/10] MM: move responsibility for setting SWP_FS_OPS to ->swap_activate NeilBrown
2022-03-29 23:49 ` [PATCH 05/10] MM: introduce ->swap_rw and use it for reads from SWP_FS_OPS swap-space NeilBrown
2022-03-29 23:49 ` [PATCH 10/10] VFS: Add FMODE_CAN_ODIRECT file flag NeilBrown
2022-03-30 10:26 ` [PATCH 00/10] MM changes to improve swap-over-NFS support David Howells
2022-03-31 1:12 ` NeilBrown [this message]
2022-04-19 15:57 ` Geert Uytterhoeven
2022-04-26 2:04 ` NeilBrown
2022-03-31 8:13 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2022-03-06 23:49 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=164868916197.25542.11845352976146070176@noble.neil.brown.name \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--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