public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: Valentin Schneider <vschneid@redhat.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"juri.lelli@redhat.com" <juri.lelli@redhat.com>,
	"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
	"dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>,
	"bsegall@google.com" <bsegall@google.com>,
	"mgorman@suse.de" <mgorman@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [外部邮件] Re: [PATCH] sched/fair: Optimize CPU iteration using for_each_cpu_and[not]
Date: Thu, 25 Sep 2025 09:50:39 +0000	[thread overview]
Message-ID: <2db9ef16b64a4e179061339b3a758a2a@baidu.com> (raw)
In-Reply-To: <xhsmhwm6zh6wr.mognet@vschneid-thinkpadt14sgen2i.remote.csb>

> > Replace open-coded CPU iteration patterns with more efficient
> > for_each_cpu_and() and for_each_cpu_andnot() macros in three locations.
> >
> > This change both simplifies the code and provides minor performance
> > improvements by using the more specialized iteration macros.
> >
> 
> TBF I'm not sure it does improve anything for the SMT cases considering we
> don't see much more than SMT8.
> 
> The task_numa_find_cpu() one I do agree makes things better.
> 
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> 
> Reviewed-by: Valentin Schneider <vschneid@redhat.com>


Ping 

Thanks

-Li


      reply	other threads:[~2025-09-25  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15  1:15 [PATCH] sched/fair: Optimize CPU iteration using for_each_cpu_and[not] lirongqing
2025-08-19 11:45 ` Valentin Schneider
2025-09-25  9:50   ` Li,Rongqing [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=2db9ef16b64a4e179061339b3a758a2a@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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