From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <riel@surriel.com>, <nathan@kernel.org>, <shy828301@gmail.com>,
<willy@infradead.org>, <kirill.shutemov@intel.com>,
<ying.huang@intel.com>, <feng.tang@intel.com>,
<zhengjun.xing@linux.intel.com>, <linux-mm@kvack.org>
Subject: Re: [RFC PATCH] mm/thp: check and bail out if page in deferred queue already
Date: Thu, 29 Dec 2022 09:29:13 +0800 [thread overview]
Message-ID: <e8568dda-c937-ed09-1506-b57dc0383edf@intel.com> (raw)
In-Reply-To: <20221228153336.73381b85d4dbd056645b94e1@linux-foundation.org>
On 12/29/2022 7:33 AM, Andrew Morton wrote:
> On Fri, 23 Dec 2022 21:52:07 +0800 Yin Fengwei <fengwei.yin@intel.com> wrote:
>
>> Kernel build regression with LLVM was reported here:
>> https://lore.kernel.org/all/Y1GCYXGtEVZbcv%2F5@dev-arch.thelio-3990X/
>> with commit f35b5d7d676e ("mm: align larger anonymous mappings on THP
>> boundaries"). And the commit f35b5d7d676e was reverted.
>>
>> It turned out the regression is related with madvise(MADV_DONTNEED)
>> was used by ld.lld.
>
> Are we able to identify a Fixes: target for this? Thanks.
I am not sure. The commit f35b5d7d676e didn't introduce this issue. It
just exposed this issue and it's reverted already. The partial THP
behavior was like this from the first day and not a regression.
Regards
Yin, Fengwei
prev parent reply other threads:[~2022-12-29 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 13:52 Yin Fengwei
2022-12-27 20:15 ` Nathan Chancellor
2022-12-29 1:14 ` Yin, Fengwei
2022-12-28 1:24 ` David Rientjes
2022-12-29 1:15 ` Yin, Fengwei
2022-12-28 2:06 ` Huang, Ying
2022-12-29 1:15 ` Yin, Fengwei
2022-12-28 23:33 ` Andrew Morton
2022-12-29 1:29 ` 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=e8568dda-c937-ed09-1506-b57dc0383edf@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=kirill.shutemov@intel.com \
--cc=linux-mm@kvack.org \
--cc=nathan@kernel.org \
--cc=riel@surriel.com \
--cc=shy828301@gmail.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=zhengjun.xing@linux.intel.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