From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Zi Yan <ziy@nvidia.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: [PATCH 0/4] Alternative fixes for migration
Date: Mon, 4 Apr 2022 20:30:02 +0100 [thread overview]
Message-ID: <20220404193006.1429250-1-willy@infradead.org> (raw)
I heartily endorse Zi Yan's minimal fixes. These patches, drawn from
my development tree and with absolutely no testing, are a different
approach to fixing the problem. I would have submitted these patches
earlier if I'd known they were needed.
I think migrate_misplaced_transhuge_page() may be missing from Zi's
patch, but maybe filesystem pages can't end up in that path? Anyway,
let me know if you like these patches better.
Matthew Wilcox (Oracle) (4):
mm/migrate: Use a folio in alloc_migration_target()
mm/migrate: Use a folio in migrate_misplaced_transhuge_page()
mm: Add vma_alloc_folio()
mm/mempolicy: Use vma_alloc_folio() in new_page()
include/linux/gfp.h | 8 +++--
mm/mempolicy.c | 38 +++++++++++++--------
mm/migrate.c | 80 +++++++++++++++------------------------------
3 files changed, 56 insertions(+), 70 deletions(-)
--
2.34.1
next reply other threads:[~2022-04-04 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 19:30 Matthew Wilcox (Oracle) [this message]
2022-04-04 19:30 ` [PATCH 1/4] mm/migrate: Use a folio in alloc_migration_target() Matthew Wilcox (Oracle)
2022-04-04 19:30 ` [PATCH 2/4] mm/migrate: Use a folio in migrate_misplaced_transhuge_page() Matthew Wilcox (Oracle)
2022-04-04 19:30 ` [PATCH 3/4] mm: Add vma_alloc_folio() Matthew Wilcox (Oracle)
2022-04-04 19:30 ` [PATCH 4/4] mm/mempolicy: Use vma_alloc_folio() in new_page() Matthew Wilcox (Oracle)
2022-04-04 19:51 ` Zi Yan
2022-04-07 13:11 ` Matthew Wilcox
2022-04-04 19:53 ` [PATCH 0/4] Alternative fixes for migration Zi Yan
2022-04-07 6:14 ` William Kucharski
2022-04-07 6:16 ` William Kucharski
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=20220404193006.1429250-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=ziy@nvidia.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).