linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@redhat.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Zi Yan <ziy@nvidia.com>, Vishal Moola <vishal.moola@gmail.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH v2 2/5] mm: migrate: add folio_isolate_movable()
Date: Wed, 4 Sep 2024 20:05:13 +0100	[thread overview]
Message-ID: <ZtivaUhjDkURvcJz@casper.infradead.org> (raw)
In-Reply-To: <20240829145456.2591719-3-wangkefeng.wang@huawei.com>

On Thu, Aug 29, 2024 at 10:54:53PM +0800, Kefeng Wang wrote:
> Like isolate_lru_page(), make isolate_movable_page() as a wrapper
> around folio_isolate_movable(), since isolate_movable_page() always

But not everything that is movable is a folio.  Look at who sets movable
ops to see counterexamples.


  reply	other threads:[~2024-09-04 19:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 14:54 [PATCH v2 0/5] mm: convert to folio_isolate_movable() Kefeng Wang
2024-08-29 14:54 ` [PATCH v2 1/5] mm: compaction: get reference before non LRU movable folio isolation Kefeng Wang
2024-08-31 14:04   ` Matthew Wilcox
2024-09-01 22:54     ` Andrew Morton
2024-09-02 10:44     ` Kefeng Wang
2024-09-04  9:57       ` Kefeng Wang
2024-09-04 19:02       ` Matthew Wilcox
2024-09-05  4:39         ` Kefeng Wang
2024-09-02  7:57   ` Baolin Wang
2024-08-29 14:54 ` [PATCH v2 2/5] mm: migrate: add folio_isolate_movable() Kefeng Wang
2024-09-04 19:05   ` Matthew Wilcox [this message]
2024-09-05  8:01     ` Kefeng Wang
2024-08-29 14:54 ` [PATCH v2 3/5] mm: migrate: convert to folio_isolate_movable() Kefeng Wang
2024-08-29 14:54 ` [PATCH v2 4/5] mm: compaction: " Kefeng Wang
2024-08-29 14:54 ` [PATCH v2 5/5] mm: migrate: remove isolate_movable_page() Kefeng Wang
2024-08-29 20:19 ` [PATCH v2 0/5] mm: convert to folio_isolate_movable() Vishal Moola

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=ZtivaUhjDkURvcJz@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=vishal.moola@gmail.com \
    --cc=wangkefeng.wang@huawei.com \
    --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).