From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S934778AbcKKSql (ORCPT <rfc822;w@1wt.eu>);
        Fri, 11 Nov 2016 13:46:41 -0500
Received: from resqmta-ch2-03v.sys.comcast.net ([69.252.207.35]:57233 "EHLO
        resqmta-ch2-03v.sys.comcast.net" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1755669AbcKKSqj (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 11 Nov 2016 13:46:39 -0500
Date: Fri, 11 Nov 2016 12:46:37 -0600 (CST)
From: Christoph Lameter <cl@linux.com>
X-X-Sender: cl@east.gentwo.org
To: Daniel Vacek <neelx.g@gmail.com>
cc: 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>,
        Peter Zijlstra <peterz@infradead.org>,
        Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] sched/rt: RT_RUNTIME_GREED sched feature
In-Reply-To: <CAA7rmPF0nQb9721MQWurRCy7E3X46hAy2qV=joK=z5U-t70NOg@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1611111242270.23136@east.gentwo.org>
References: <fa5b1b55d8934c6a0e02e04a7ad6afdf4012c2e0.1478506194.git.bristot@redhat.com> <20161108115958.GO3142@twins.programming.kicks-ass.net> <20161108090740.4226ffc9@gandalf.local.home> <20161108165133.GI3117@twins.programming.kicks-ass.net>
 <20161108121710.3e7eb664@gandalf.local.home> <20161108180548.GN3117@twins.programming.kicks-ass.net> <f4095990-3fa0-ac2f-7277-3b8f0cdbc333@redhat.com> <20161108195015.GP3117@twins.programming.kicks-ass.net> <8a80c2c2-3803-5648-67b2-4dee7381d5a6@redhat.com>
 <CAA7rmPF0nQb9721MQWurRCy7E3X46hAy2qV=joK=z5U-t70NOg@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII
X-CMAE-Envelope: MS4wfM6Jl6JWH3arcWMYfLHDzpO8y66RSSIwax2qjqNgR8soNFzINoYR+3tVal6nKI3GUKHtErVrHD+l01DkAYfkNDIqSdc1qo3WTwq6rFztr/3zoEth2ee2
 3EgEEQ+NcMyF1oy/BWlMnEyM0f2QxqqJgQ5aWobBQH+jVn8/rnCmRwFA77ogpGLK7bex8cYcXiipE/44XaNc48/NBXEaUeOm2oza3dWLr8xq6UxKoG02vgiv
 CRZEBVzqNtxmlG/CQFFYNJU47nhsP3wa7+3cLXY2j7zBFaBdoJ82vt+thLhbvskbVppl6otvvU4oI+hA9WJDiQ3JULjN3tJLXIgfKhfu9/KHrioT+nJAd08M
 8YRVQpF8CxJTzULLKkACyZ5Ebk5/IpWeY3np26REv2Eke+Celc0=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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?