linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
	John Stultz <john.stultz@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] timer: Use static_branch_likely() for timers_nohz_active
Date: Tue, 10 Aug 2021 18:00:16 +0200	[thread overview]
Message-ID: <87im0dqohb.ffs@tglx> (raw)
In-Reply-To: <20210624163218.39ae3ec6@xhacker.debian>

Jisheng,

On Thu, Jun 24 2021 at 16:32, Jisheng Zhang wrote:

> The static key timers_nohz_active is likely to be true, so use
> static_branch_likely() to reflect this fact.

you still lack any justification for your statement that NOHZ active is
likely.

It might be likely for your system, but is this true in general?

Thanks,

        tglx

  reply	other threads:[~2021-08-10 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24  8:32 [PATCH v2] timer: Use static_branch_likely() for timers_nohz_active Jisheng Zhang
2021-08-10 16:00 ` Thomas Gleixner [this message]
2021-08-20 10:18   ` Jisheng Zhang

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=87im0dqohb.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).