From: Peter Zijlstra <peterz@infradead.org>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@gmail.com>
Subject: Re: [PATCH] sched/rt: Rework for_each_process_thread() iterations in tg_has_rt_tasks()
Date: Wed, 25 Apr 2018 19:55:35 +0200 [thread overview]
Message-ID: <20180425175535.GC4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <152415882713.2054.8734093066910722403.stgit@localhost.localdomain>
On Thu, Apr 19, 2018 at 08:29:01PM +0300, Kirill Tkhai wrote:
> tg_rt_schedulable() iterates over all child task groups,
> while tg_has_rt_tasks() iterates over all linked tasks.
> In case of systems with big number of tasks, this may
> take a lot of time.
So you're actually using RT cgroups?
Some of us recently considered removing that thing entirely because most
distro's don't actually use it at all -- and it's broken from a RT POV.
That would then clear the slate to try and implement something new.
But if you're actually using this stuff, that would complicate matters.
next prev parent reply other threads:[~2018-04-25 17:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 17:29 [PATCH] sched/rt: Rework for_each_process_thread() iterations in tg_has_rt_tasks() Kirill Tkhai
2018-04-20 9:25 ` Juri Lelli
2018-04-20 9:43 ` Kirill Tkhai
2018-04-20 10:06 ` [PATCH v2] " Kirill Tkhai
2018-04-20 14:11 ` Juri Lelli
2018-04-20 14:30 ` Kirill Tkhai
2018-04-20 15:27 ` Juri Lelli
2018-04-25 15:42 ` Kirill Tkhai
2018-04-25 19:49 ` Peter Zijlstra
2018-04-26 9:54 ` [PATCH v3]sched/rt: Stop " Kirill Tkhai
2020-01-23 21:56 ` Phil Auld
2020-01-24 9:09 ` Kirill Tkhai
2020-01-27 16:30 ` Phil Auld
2020-01-27 16:43 ` Peter Zijlstra
2020-01-27 16:56 ` Phil Auld
2020-01-27 17:00 ` Peter Zijlstra
2020-01-27 17:45 ` Phil Auld
2018-04-20 10:58 ` [PATCH] sched/rt: Rework " Juri Lelli
2018-04-20 11:21 ` Kirill Tkhai
2018-04-25 17:55 ` Peter Zijlstra [this message]
2018-04-26 9:26 ` Kirill Tkhai
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=20180425175535.GC4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=juri.lelli@gmail.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 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.