From: Peter Zijlstra <peterz@infradead.org>
To: Benjamin Segall <bsegall@google.com>
Cc: shrikanth hegde <sshegde@linux.vnet.ibm.com>,
mingo@redhat.com, Vincent Guittot <vincent.guittot@linaro.org>,
dietmar.eggemann@arm.com, Thomas Gleixner <tglx@linutronix.de>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Arjan van de Ven <arjan@linux.intel.com>,
svaidy@linux.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched/fair: Interleave cfs bandwidth timers for improved single thread performance at low utilization
Date: Wed, 22 Feb 2023 10:36:40 +0100 [thread overview]
Message-ID: <Y/XiKKDLcejSYc6+@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <xm267cwa4ruo.fsf@google.com>
On Tue, Feb 21, 2023 at 01:43:27PM -0800, Benjamin Segall wrote:
> The value should never come up, so it's just a question of if it's fine
> to call get_random_* in early contexts, which I don't know offhand.
Should be, scheduler init is quite late as things go and people have
been pushing the random init earlier and earlier.
next prev parent reply other threads:[~2023-02-22 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 15:24 [RFC PATCH] sched/fair: Interleave cfs bandwidth timers for improved single thread performance at low utilization shrikanth hegde
2023-02-20 17:38 ` Peter Zijlstra
2023-02-21 18:53 ` shrikanth hegde
2023-02-21 21:43 ` Benjamin Segall
2023-02-22 9:36 ` Peter Zijlstra [this message]
[not found] <20230214120502.934324-1-sshegde@linux.vnet.ibm.com>
2023-02-14 21:37 ` Benjamin Segall
2023-02-15 11:01 ` shrikanth hegde
2023-02-15 21:32 ` Benjamin Segall
2023-02-16 19:57 ` shrikanth hegde
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=Y/XiKKDLcejSYc6+@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arjan@linux.intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=sshegde@linux.vnet.ibm.com \
--cc=svaidy@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.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).