From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Lameter <cl@linux.com>
Cc: Daniel Vacek <neelx.g@gmail.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] sched/rt: RT_RUNTIME_GREED sched feature
Date: Mon, 14 Nov 2016 10:20:33 +0100 [thread overview]
Message-ID: <20161114092033.GS3117@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1611131253160.7920@east.gentwo.org>
On Sun, Nov 13, 2016 at 12:53:28PM -0600, Christoph Lameter wrote:
> On Fri, 11 Nov 2016, Peter Zijlstra wrote:
>
> > On Fri, Nov 11, 2016 at 12:46:37PM -0600, Christoph Lameter wrote:
> > > On Thu, 10 Nov 2016, Daniel Vacek wrote:
> > >
> > > > I believe Daniel's patches are the best thing we can do in current
> > > > situation as the behavior now seems rather buggy and does not provide above
> > > > mentioned expectations set when rt throttling was merged with default
> > > > budget of 95% of CPU time. Nor if you configure so that it does (by
> > > > disabling RT_RUNTIME_SHARE), it also forces CPUs to go idle needlessly when
> > > > there still can be rt task running not really starving anyone. At least
> > > > till a proper rework of rt scheduling with DL Server is implemented.
> > >
> > > This looks like a fix for a bug and the company I work for is suffering
> > > as a result. Could we please merge that ASAP?
> > >
> >
> > What bug? And no, the patch has as many technical issues as it has
> > conceptual ones.
>
> There is a deadlock, Peter!!!
Describe please? Also, have you tried disabling RT_RUNTIME_SHARE ?
prev parent reply other threads:[~2016-11-14 9:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 8:17 [PATCH] sched/rt: RT_RUNTIME_GREED sched feature Daniel Bristot de Oliveira
2016-11-07 10:31 ` Tommaso Cucinotta
2016-11-07 13:51 ` Daniel Bristot de Oliveira
2016-11-07 18:03 ` Tommaso Cucinotta
2016-11-07 18:06 ` Luca Abeni
2016-11-08 7:55 ` luca abeni
2016-11-08 10:30 ` Juri Lelli
2016-11-07 16:55 ` Christoph Lameter
2016-11-07 18:32 ` Steven Rostedt
2016-11-07 18:49 ` Daniel Bristot de Oliveira
2016-11-07 19:16 ` Steven Rostedt
2016-11-07 19:30 ` Christoph Lameter
2016-11-07 19:47 ` Steven Rostedt
2016-11-07 19:54 ` Christoph Lameter
2016-11-07 20:00 ` Steven Rostedt
2016-11-07 20:06 ` Daniel Bristot de Oliveira
2016-11-07 20:16 ` Steven Rostedt
2016-11-07 20:33 ` Daniel Bristot de Oliveira
2016-11-07 20:44 ` Steven Rostedt
2016-11-08 9:22 ` [PATCH] sched/rt: Change default setup for RT THROTTLING Daniel Bristot de Oliveira
2016-11-08 23:42 ` [PATCH] sched/rt: RT_RUNTIME_GREED sched feature Christoph Lameter
2016-11-07 18:22 ` Clark Williams
2016-11-07 18:30 ` Steven Rostedt
2016-11-07 18:38 ` Daniel Bristot de Oliveira
2016-11-07 18:39 ` Clark Williams
2016-11-08 11:59 ` Peter Zijlstra
2016-11-08 14:07 ` Steven Rostedt
2016-11-08 16:51 ` Peter Zijlstra
2016-11-08 17:17 ` Steven Rostedt
2016-11-08 18:05 ` Peter Zijlstra
2016-11-08 19:29 ` Daniel Bristot de Oliveira
2016-11-08 19:50 ` Peter Zijlstra
2016-11-09 13:33 ` Daniel Bristot de Oliveira
[not found] ` <CAA7rmPF0nQb9721MQWurRCy7E3X46hAy2qV=joK=z5U-t70NOg@mail.gmail.com>
2016-11-11 18:46 ` Christoph Lameter
2016-11-11 22:53 ` Peter Zijlstra
2016-11-13 18:53 ` Christoph Lameter
2016-11-14 9:20 ` 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=20161114092033.GS3117@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neelx.g@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tommaso.cucinotta@sssup.it \
/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.