From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: <akpm@linux-foundation.org>, <linux-mm@kvack.org>
Cc: Tony Luck <tony.luck@intel.com>,
Miaohe Lin <linmiaohe@huawei.com>, <nao.horiguchi@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
Muchun Song <muchun.song@linux.dev>,
Benjamin LaHaise <bcrl@kvack.org>, <jglisse@redhat.com>,
Zi Yan <ziy@nvidia.com>, Jiaqi Yan <jiaqiyan@google.com>,
Hugh Dickins <hughd@google.com>,
Vishal Moola <vishal.moola@gmail.com>,
Alistair Popple <apopple@nvidia.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH 0/5] mm: cleanup MIGRATE_SYNC_NO_COPY mode
Date: Fri, 24 May 2024 13:28:38 +0800 [thread overview]
Message-ID: <20240524052843.182275-1-wangkefeng.wang@huawei.com> (raw)
Commit 2916ecc0f9d4 ("mm/migrate: new migrate mode MIGRATE_SYNC_NO_COPY")
introduce a new MIGRATE_SYNC_NO_COPY mode to allow to offload the copy to
a device DMA engine, which is only used __migrate_device_pages() to decide
whether or not copy the old page, and the MIGRATE_SYNC_NO_COPY mode only
used in hmm, a easy way is just to call the folio_migrate_mapping() and
folio_migrate_flags(), which help to remove the MIGRATE_SYNC_NO_COPY
mode.
---
This is splitted from "mm: migrate: support poison recover from migrate
folio"[1] to make it easier review and hope it merged firstly since no
more comment for a long time, rebase on next-20240523 and only patch2
changed a bit due to commit e18a9faf06c2.
[1] https://lore.kernel.org/linux-mm/20240424135929.2847185-9-wangkefeng.wang@huawei.com/
Kefeng Wang (5):
mm: migrate: simplify __buffer_migrate_folio()
mm: migrate_device: use a newfolio in __migrate_device_pages()
mm: migrate_device: unify migrate folio for MIGRATE_SYNC_NO_COPY
mm: migrate: remove migrate_folio_extra()
mm: remove MIGRATE_SYNC_NO_COPY mode
fs/aio.c | 12 +--------
fs/hugetlbfs/inode.c | 5 +---
include/linux/migrate.h | 2 --
include/linux/migrate_mode.h | 5 ----
mm/balloon_compaction.c | 8 ------
mm/migrate.c | 51 +++++++++---------------------------
mm/migrate_device.c | 22 +++++++++-------
mm/zsmalloc.c | 8 ------
8 files changed, 27 insertions(+), 86 deletions(-)
--
2.27.0
next reply other threads:[~2024-05-24 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 5:28 Kefeng Wang [this message]
2024-05-24 5:28 ` [PATCH 1/5] mm: migrate: simplify __buffer_migrate_folio() Kefeng Wang
2024-05-24 5:28 ` [PATCH 2/5] mm: migrate_device: use a newfolio in __migrate_device_pages() Kefeng Wang
2024-05-24 5:28 ` [PATCH 3/5] mm: migrate_device: unify migrate folio for MIGRATE_SYNC_NO_COPY Kefeng Wang
2024-06-07 20:23 ` Jane Chu
2024-05-24 5:28 ` [PATCH 4/5] mm: migrate: remove migrate_folio_extra() Kefeng Wang
2024-06-07 20:38 ` Jane Chu
2024-05-24 5:28 ` [PATCH 5/5] mm: remove MIGRATE_SYNC_NO_COPY mode Kefeng Wang
2024-06-07 21:27 ` Jane Chu
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=20240524052843.182275-1-wangkefeng.wang@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=bcrl@kvack.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=jiaqiyan@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=tony.luck@intel.com \
--cc=vishal.moola@gmail.com \
--cc=willy@infradead.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