All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <willy@infradead.org>, David Hildenbrand <david@redhat.com>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>,
	Oscar Salvador <osalvador@suse.de>, Zi Yan <ziy@nvidia.com>,
	Hugh Dickins <hughd@google.com>, Jonathan Corbet <corbet@lwn.net>,
	<linux-mm@kvack.org>, Vishal Moola <vishal.moola@gmail.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH v2 00/10] mm: remove isolate_lru_page() and isolate_movable_page()
Date: Thu, 25 Apr 2024 16:40:18 +0800	[thread overview]
Message-ID: <20240425084028.3888403-1-wangkefeng.wang@huawei.com> (raw)

Rework to unify Huge/LRU/non-LRU folio isolation in do_migrate_range()
and isolate_migratepages_block(), then convert isolate_movable/lru_page()
to folio_isolate_movable/lru(), finally cleanup isolate_moveable/lru_page().

v2:
- rename isolate_movable_folio() to isolate_movable_folio() and address
  the issue about it, per Zi Yan, Vishal Moola
- check hwpoisoned page firstly in do_migrate_range(), which help
  to unify Hugepage/LRU/non-LRU movable folio isolation, suggested by
  Zi Yan
- re-order patches, per Vishal Moola.

Kefeng Wang (10):
  mm: memory_hotplug: check hwpoisoned page firstly in
    do_migrate_range()
  mm: add isolate_folio_to_list()
  mm: memory_hotplug: unify Huge/LRU/non-LRU folio isolation
  mm: compaction: try get reference before non-lru movable folio
    migration
  mm: migrate: add folio_isolate_movable()
  mm: compaction: use folio_isolate_movable()
  mm: migrate: use folio_isolate_movable()
  mm: migrate: remove isolate_movable_page()
  mm: migrate_device: use more folio in migrate_device_unmap()
  mm: remove isolate_lru_page()

 Documentation/mm/page_migration.rst           |  6 +-
 Documentation/mm/unevictable-lru.rst          |  2 +-
 .../translations/zh_CN/mm/page_migration.rst  |  6 +-
 include/linux/migrate.h                       |  5 +-
 mm/compaction.c                               | 38 ++++----
 mm/filemap.c                                  |  2 +-
 mm/folio-compat.c                             |  7 --
 mm/internal.h                                 |  3 +-
 mm/khugepaged.c                               |  6 +-
 mm/memory-failure.c                           | 21 +---
 mm/memory_hotplug.c                           | 95 +++++++++++--------
 mm/migrate.c                                  | 60 ++++++++----
 mm/migrate_device.c                           | 18 ++--
 mm/swap.c                                     |  2 +-
 14 files changed, 145 insertions(+), 126 deletions(-)

-- 
2.27.0



             reply	other threads:[~2024-04-25  8:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  8:40 Kefeng Wang [this message]
2024-04-25  8:40 ` [PATCH v2 01/10] mm: memory_hotplug: check hwpoisoned page firstly in do_migrate_range() Kefeng Wang
2024-04-27  3:57   ` kernel test robot
2024-04-28  0:49     ` Kefeng Wang
2024-04-27  5:40   ` kernel test robot
2024-04-27  7:23   ` kernel test robot
2024-04-25  8:40 ` [PATCH v2 02/10] mm: add isolate_folio_to_list() Kefeng Wang
2024-04-25  8:40 ` [PATCH v2 03/10] mm: memory_hotplug: unify Huge/LRU/non-LRU folio isolation Kefeng Wang
2024-04-25  8:40 ` [PATCH v2 04/10] mm: compaction: try get reference before non-lru movable folio migration Kefeng Wang
2024-04-25  8:40 ` [PATCH v2 05/10] mm: migrate: add folio_isolate_movable() Kefeng Wang
2024-04-25  8:40 ` [PATCH v2 06/10] mm: compaction: use folio_isolate_movable() Kefeng Wang
2024-04-25  8:40 ` [PATCH v2 07/10] mm: migrate: " Kefeng Wang
2024-04-25  8:40 ` [PATCH v2 08/10] mm: migrate: remove isolate_movable_page() Kefeng Wang
2024-04-25  8:40 ` [PATCH v2 09/10] mm: migrate_device: use more folio in migrate_device_unmap() Kefeng Wang
2024-04-25  9:31   ` David Hildenbrand
2024-04-25 11:05     ` Kefeng Wang
2024-04-25  8:40 ` [PATCH v2 10/10] mm: remove isolate_lru_page() Kefeng Wang

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=20240425084028.3888403-1-wangkefeng.wang@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.