From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Youssef Esmat <youssefesmat@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
bsegall@google.com, mingo@kernel.org, vincent.guittot@linaro.org,
juri.lelli@redhat.com, dietmar.eggemann@arm.com, mgorman@suse.de,
bristot@redhat.com, corbet@lwn.net, qyousef@layalina.io,
chris.hyser@oracle.com, patrick.bellasi@matbug.net,
pjt@google.com, pavel@ucw.cz, qperret@google.com,
tim.c.chen@linux.intel.com, joshdon@google.com, timj@gnu.org,
kprateek.nayak@amd.com, yu.c.chen@intel.com,
joel@joelfernandes.org, efault@gmx.de, tglx@linutronix.de,
wuyun.abel@bytedance.com
Subject: Re: [PATCH] sched/eevdf: Toggle eligibility through sched_feat
Date: Mon, 16 Oct 2023 18:52:08 +0200 [thread overview]
Message-ID: <20231016165208.GH33217@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20231016112851.5cc0ccad@gandalf.local.home>
On Mon, Oct 16, 2023 at 11:28:51AM -0400, Steven Rostedt wrote:
> The main point is, our testing is not around any single benchmark that we
> are trying to make happy. We really are looking at what makes the user base
> run better in the real world.
This is a key (har-har) performance indicator for you guys though, I've
seen it mentioned before (with the core-scheduling crud IIRC).
As such it would be good to capture in a stand alone program and share.
prev parent reply other threads:[~2023-10-16 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 3:02 Youssef Esmat
2023-10-13 6:50 ` Mike Galbraith
2023-10-15 10:44 ` Peter Zijlstra
2023-10-16 13:33 ` Tor Vic
2023-10-16 15:28 ` Steven Rostedt
2023-10-16 16:52 ` Peter Zijlstra [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=20231016165208.GH33217@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=chris.hyser@oracle.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=efault@gmx.de \
--cc=joel@joelfernandes.org \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=patrick.bellasi@matbug.net \
--cc=pavel@ucw.cz \
--cc=pjt@google.com \
--cc=qperret@google.com \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=timj@gnu.org \
--cc=vincent.guittot@linaro.org \
--cc=wuyun.abel@bytedance.com \
--cc=youssefesmat@chromium.org \
--cc=yu.c.chen@intel.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
Powered by JetHome