From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "Yang Shi" <shy828301@gmail.com>, "Yu Zhao" <yuzhao@google.com>,
"Minchan Kim" <minchan@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>, 韩天硕 <hantianshuo@iie.ac.cn>,
mawupeng <mawupeng1@huawei.com>
Subject: Re: (resend)WARNING: trying to isolate tail page in isolate_lru_page
Date: Sat, 27 Aug 2022 08:24:08 +0800 [thread overview]
Message-ID: <8e59833e-8fe5-2dbb-58fc-e4f6b91853f6@intel.com> (raw)
In-Reply-To: <Ywj/wCmmbntDwMPE@casper.infradead.org>
On 8/27/2022 1:15 AM, Matthew Wilcox wrote:
> On Fri, Aug 26, 2022 at 11:20:58AM +0800, Yin, Fengwei wrote:
>> On 8/26/2022 2:46 AM, Matthew Wilcox wrote:
>>> There's a number of ways of solving this. I'm interested in seeing
>>> which one Minchan thinks is best.
>>
>> My understanding is:
>> PageTransCompound() return false for compound page if THP is disabled
>> in kernel config. Replacing PageTransCompound() with PageCompound()
>> could work here. But for the long term, folio should be the answer. :).
>
> Yes, ultimately, isolate_lru_page() is going away as an interface
> and one will have to call folio_isolate_lru(). But should
> madvise_cold_or_pageout_pte_range() even be getting called for VMAs
> which are mmaps of af_packet? can_madv_lru_vma() rules out a number
> of different types of VMA; should it also be ruling out af_packet VMAs?
> If so, how?
Thanks a lot for the information which helps me to understand the real
concern here.
Regards
Yin, Fengwei
prev parent reply other threads:[~2022-08-27 0:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 14:40 (resend)WARNING: trying to isolate tail page in isolate_lru_page 韩天硕
2022-08-25 16:50 ` Yu Zhao
2022-08-25 18:23 ` Matthew Wilcox
2022-08-25 18:37 ` Yu Zhao
2022-08-25 18:40 ` Yang Shi
2022-08-25 18:46 ` Matthew Wilcox
2022-08-26 3:20 ` Yin, Fengwei
2022-08-26 16:56 ` Minchan Kim
2022-08-26 18:23 ` Yang Shi
2022-08-26 22:58 ` Minchan Kim
2022-08-27 0:48 ` Yin, Fengwei
2022-08-26 17:15 ` Matthew Wilcox
2022-08-26 17:27 ` Yu Zhao
2022-08-26 17:53 ` Minchan Kim
2022-08-26 17:58 ` Yu Zhao
2022-08-26 18:02 ` Matthew Wilcox
2022-08-26 18:19 ` Yang Shi
2022-08-26 23:12 ` Minchan Kim
2022-08-27 0:24 ` Yin, Fengwei [this message]
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=8e59833e-8fe5-2dbb-58fc-e4f6b91853f6@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hantianshuo@iie.ac.cn \
--cc=linux-mm@kvack.org \
--cc=mawupeng1@huawei.com \
--cc=minchan@kernel.org \
--cc=shy828301@gmail.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.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.