From: Peter Zijlstra <peterz@infradead.org>
To: Patrick Bellasi <patrick.bellasi@arm.com>
Cc: subhra mazumdar <subhra.mazumdar@oracle.com>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, steven.sistare@oracle.com,
dhaval.giani@oracle.com, daniel.lezcano@linaro.org,
vincent.guittot@linaro.org, viresh.kumar@linaro.org,
tim.c.chen@linux.intel.com, mgorman@techsingularity.net,
Paul Turner <pjt@google.com>,
riel@surriel.com, morten.rasmussen@arm.com
Subject: Re: [RESEND PATCH v3 0/7] Improve scheduler scalability for fast path
Date: Mon, 1 Jul 2019 16:06:42 +0200 [thread overview]
Message-ID: <20190701140642.GX3402@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190701135552.kb4os6bxxhh2lyw6@e110439-lin>
On Mon, Jul 01, 2019 at 02:55:52PM +0100, Patrick Bellasi wrote:
> On 01-Jul 11:02, Peter Zijlstra wrote:
> > Hmmm?
>
> Just one more requirement I think it's worth to consider since the
> beginning: CGroups support
>
> That would be very welcome interface. Just because is so much more
> convenient (and safe) to set these bias on a group of tasks depending
> on their role in the system.
>
> Do you have any idea on how we can expose such a "lantency-nice"
> property via CGroups? It's very similar to cpu.shares but it does not
> represent a resource which can be partitioned.
If the latency_nice idea lives; exactly like the normal nice? That is;
IIRC cgroupv2 has a nice value interface (see cpu_weight_nice_*()).
But yes, this isn't a resource per se; just a shared attribute like
thing.
next prev parent reply other threads:[~2019-07-01 14:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 1:29 [RESEND PATCH v3 0/7] Improve scheduler scalability for fast path subhra mazumdar
2019-06-27 1:29 ` [PATCH v3 1/7] sched: limit cpu search in select_idle_cpu subhra mazumdar
2019-06-28 18:47 ` Parth Shah
2019-06-28 22:21 ` Subhra Mazumdar
2019-06-27 1:29 ` [PATCH v3 2/7] sched: introduce per-cpu var next_cpu to track search limit subhra mazumdar
2019-06-27 1:29 ` [PATCH v3 3/7] sched: rotate the cpu search window for better spread subhra mazumdar
2019-06-28 11:54 ` Srikar Dronamraju
2019-06-28 22:34 ` Subhra Mazumdar
2019-06-28 18:36 ` Parth Shah
2019-06-28 22:14 ` Subhra Mazumdar
2019-06-27 1:29 ` [PATCH v3 4/7] sched: add sched feature to disable idle core search subhra mazumdar
2019-06-27 1:29 ` [PATCH v3 5/7] sched: SIS_CORE " subhra mazumdar
2019-06-28 19:01 ` Parth Shah
2019-06-28 22:29 ` Subhra Mazumdar
2019-07-01 9:57 ` Parth Shah
2019-07-01 20:37 ` Subhra Mazumdar
2019-07-04 12:34 ` Parth Shah
2019-07-14 1:16 ` Subhra Mazumdar
2019-06-27 1:29 ` [PATCH v3 6/7] x86/smpboot: introduce per-cpu variable for HT siblings subhra mazumdar
2019-06-27 6:51 ` Thomas Gleixner
2019-06-27 6:54 ` Thomas Gleixner
2019-06-28 1:06 ` Subhra Mazumdar
2019-06-28 1:02 ` Subhra Mazumdar
2019-06-27 1:29 ` [PATCH v3 7/7] sched: use per-cpu variable cpumask_weight_sibling subhra mazumdar
2019-07-01 9:02 ` [RESEND PATCH v3 0/7] Improve scheduler scalability for fast path Peter Zijlstra
2019-07-01 13:55 ` Patrick Bellasi
2019-07-01 14:04 ` Peter Zijlstra
2019-07-08 22:32 ` Tim Chen
2019-07-01 14:06 ` Peter Zijlstra [this message]
2019-07-02 0:01 ` Subhra Mazumdar
2019-07-02 8:54 ` Patrick Bellasi
2019-07-03 3:52 ` Subhra Mazumdar
2019-07-04 11:35 ` Parth Shah
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=20190701140642.GX3402@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.lezcano@linaro.org \
--cc=dhaval.giani@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=pjt@google.com \
--cc=riel@surriel.com \
--cc=steven.sistare@oracle.com \
--cc=subhra.mazumdar@oracle.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.