From: Ye Liu <ye.liu@linux.dev>
To: Markus Elfring <Markus.Elfring@web.de>, Ye Liu <liuye@kylinos.cn>,
linux-mm@kvack.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Sidhartha Kumar <sidhartha.kumar@oracle.com>
Subject: Re: [PATCH v3] mm/page_alloc: Consolidate unlikely handling in page_expected_state
Date: Wed, 26 Mar 2025 17:34:14 +0800 [thread overview]
Message-ID: <7c278ba6-c1a2-4ef7-a4ac-48c233dce7a3@linux.dev> (raw)
In-Reply-To: <0ceb4ab8-adb5-46bf-98e4-61a1bd908e20@web.de>
在 2025/3/26 16:48, Markus Elfring 写道:
>> Consolidates the handling of
> …
>> This change simplifies
> …
>> ---
>> V3: Delete 'This patch'.
> How good does such information fit to the wording requirement “imperative mood”?
> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.14#n94
How about this?
Consolidate the handling of unlikely conditions in the page_expected_state
function to reduce code duplication and improve readability.
Move the logic for handling __PG_HWPOISON flags from the check_new_page_bad
function to the page_expected_state function, and remove check_new_page_bad.
Call bad_page directly from the check_new_page function if the page has
unexpected flags.
Simplify the code by reducing the number of functions and centralizing the
handling of unlikely conditions.
> …
>> ---
>> ---
>> mm/page_alloc.c | 24 ++++++++----------------
> How do you think about to omit redundant marker lines?
--- delete this one?
---
mm/page_alloc.c | 24 ++++++++----------------
like this ?
V2: return true instead of false in the PageHWPoison branch.
---
mm/page_alloc.c | 24 ++++++++----------------
Thanks for pointing out the formatting issue.
I would like to get your approval on the above changes before I send patch v4.
> Regards,
> Markus
next prev parent reply other threads:[~2025-03-26 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 1:17 Ye Liu
2025-03-26 8:48 ` Markus Elfring
2025-03-26 9:34 ` Ye Liu [this message]
2025-03-27 15:05 ` [v3] " Markus Elfring
2025-03-28 1:27 ` Ye Liu
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=7c278ba6-c1a2-4ef7-a4ac-48c233dce7a3@linux.dev \
--to=ye.liu@linux.dev \
--cc=Markus.Elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=sidhartha.kumar@oracle.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