From: Ye Liu <ye.liu@linux.dev>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Ye Liu <liuye@kylinos.cn>, Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/slub: Refactor note_cmpxchg_failure for better readability
Date: Mon, 8 Sep 2025 16:56:40 +0800 [thread overview]
Message-ID: <c089b941-97c7-4392-828f-923e8da3510a@linux.dev> (raw)
In-Reply-To: <aL6WTrXczZJYUoGb@hyeyoo>
在 2025/9/8 16:39, Harry Yoo 写道:
> On Mon, Sep 08, 2025 at 03:19:21PM +0800, Ye Liu wrote:
>> From: Ye Liu <liuye@kylinos.cn>
>>
>> Use IS_ENABLED() and standard if-else to make the code clearer.
>>
>> Signed-off-by: Ye Liu <liuye@kylinos.cn>
>> ---
>
> Looks good to me,
> Reviewed-by: Harry Yoo <harry.yoo@oracle.com>
>
> with a nit,
>
>> mm/slub.c | 10 ++++------
>> 1 file changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/mm/slub.c b/mm/slub.c
>> index 30003763d224..34853c0441a6 100644
>> --- a/mm/slub.c
>> +++ b/mm/slub.c
>> @@ -3064,18 +3064,16 @@ static inline void note_cmpxchg_failure(const char *n,
>>
>> pr_info("%s %s: cmpxchg redo ", n, s->name);
>>
>> -#ifdef CONFIG_PREEMPTION
>> - if (tid_to_cpu(tid) != tid_to_cpu(actual_tid))
>> + if (IS_ENABLED(CONFIG_PREEMPTION) && tid_to_cpu(tid) != tid_to_cpu(actual_tid)) {
>
> nit: insert newline after && as it's more than 80 columns?
I noticed this too, but using the script ./scripts/checkpatch.pl , there were no warnings.
$ ./scripts/checkpatch.pl 0001-mm-slub-Refactor-note_cmpxchg_failure-for-better-rea.patch
total: 0 errors, 0 warnings, 22 lines checked
0001-mm-slub-Refactor-note_cmpxchg_failure-for-better-rea.patch has no obvious style problems and is ready for submission.
>
>> pr_warn("due to cpu change %d -> %d\n",
>> tid_to_cpu(tid), tid_to_cpu(actual_tid));
>> - else
>> -#endif
>> - if (tid_to_event(tid) != tid_to_event(actual_tid))
>> + } else if (tid_to_event(tid) != tid_to_event(actual_tid)) {
>> pr_warn("due to cpu running other code. Event %ld->%ld\n",
>> tid_to_event(tid), tid_to_event(actual_tid));
>> - else
>> + } else {
>> pr_warn("for unknown reason: actual=%lx was=%lx target=%lx\n",
>> actual_tid, tid, next_tid(tid));
>> + }
>> #endif
>> stat(s, CMPXCHG_DOUBLE_CPU_FAIL);
>> }
>> --
>> 2.43.0
--
Thanks,
Ye Liu
next prev parent reply other threads:[~2025-09-08 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 7:19 Ye Liu
2025-09-08 8:39 ` Harry Yoo
2025-09-08 8:56 ` Ye Liu [this message]
2025-09-08 9:21 ` Harry Yoo
2025-09-08 9:33 ` 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=c089b941-97c7-4392-828f-923e8da3510a@linux.dev \
--to=ye.liu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/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