public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Yuan ZhaoXiong <yuanzhaoxiong@baidu.com>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	bristot@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: Optimize housekeeping_cpumask in for_each_cpu_and
Date: Mon, 31 May 2021 12:37:26 +0200	[thread overview]
Message-ID: <YLS8ZsV40lh3vuA5@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <YK9pGoOxA7gVi1S2@hirez.programming.kicks-ass.net>

On Thu, May 27, 2021 at 11:40:42AM +0200, Peter Zijlstra wrote:
> On Sat, Apr 17, 2021 at 11:01:37PM +0800, Yuan ZhaoXiong wrote:
> > On a 128 cores AMD machine, there are 8 cores in nohz_full mode, and
> > the others are used for housekeeping. When many housekeeping cpus are
> > in idle state, we can observe huge time burn in the loop for searching
> > nearest busy housekeeper cpu by ftrace.
> > 
> >    9)               |              get_nohz_timer_target() {
> >    9)               |                housekeeping_test_cpu() {
> >    9)   0.390 us    |                  housekeeping_get_mask.part.1();
> >    9)   0.561 us    |                }
> >    9)   0.090 us    |                __rcu_read_lock();
> >    9)   0.090 us    |                housekeeping_cpumask();
> >    9)   0.521 us    |                housekeeping_cpumask();
> >    9)   0.140 us    |                housekeeping_cpumask();
> > 
> >    ...
> > 
> >    9)   0.500 us    |                housekeeping_cpumask();
> >    9)               |                housekeeping_any_cpu() {
> >    9)   0.090 us    |                  housekeeping_get_mask.part.1();
> >    9)   0.100 us    |                  sched_numa_find_closest();
> >    9)   0.491 us    |                }
> >    9)   0.100 us    |                __rcu_read_unlock();
> >    9) + 76.163 us   |              }
> > 
> > for_each_cpu_and() is a micro function, so in get_nohz_timer_target()
> > function the
> >         for_each_cpu_and(i, sched_domain_span(sd),
> >                 housekeeping_cpumask(HK_FLAG_TIMER))
> > equals to below:
> >         for (i = -1; i = cpumask_next_and(i, sched_domain_span(sd),
> >                 housekeeping_cpumask(HK_FLAG_TIMER)), i < nr_cpu_ids;)
> > That will cause that housekeeping_cpumask() will be invoked many times.
> > The housekeeping_cpumask() function returns a const value, so it is
> > unnecessary to invoke it every time. This patch can minimize the worst
> > searching time from ~76us to ~16us in my testing.
> > 
> > Similarly, the find_new_ilb() function has the same problem.
> > 
> > Signed-off-by: Yuan ZhaoXiong <yuanzhaoxiong@baidu.com>
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> 
> Just noticed, this SoB chain isn't valid. What do I do with Li's entry?

I'm dropping this patch, please resend with a valid SoB chain.

  reply	other threads:[~2021-05-31 10:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 15:01 [PATCH] sched: Optimize housekeeping_cpumask in for_each_cpu_and Yuan ZhaoXiong
2021-04-19  9:56 ` Peter Zijlstra
2021-04-20  6:44   ` Yuan,Zhaoxiong
2021-04-30  6:38     ` Yuan,Zhaoxiong
2021-05-20  8:36 ` Peter Zijlstra
2021-05-27  9:40 ` Peter Zijlstra
2021-05-31 10:37   ` Peter Zijlstra [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-02  2:03 Yuan ZhaoXiong
2021-06-02  7:57 ` Peter Zijlstra
2021-06-06 13:11 Yuan ZhaoXiong

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=YLS8ZsV40lh3vuA5@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bristot@redhat.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=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=yuanzhaoxiong@baidu.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