Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938647AbcKKWxc (ORCPT ); Fri, 11 Nov 2016 17:53:32 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:60963 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935421AbcKKWxa (ORCPT ); Fri, 11 Nov 2016 17:53:30 -0500 Date: Fri, 11 Nov 2016 23:53:28 +0100 From: Peter Zijlstra To: Christoph Lameter Cc: Daniel Vacek , Daniel Bristot de Oliveira , Tommaso Cucinotta , LKML , linux-rt-users , Steven Rostedt , Ingo Molnar Subject: Re: [PATCH] sched/rt: RT_RUNTIME_GREED sched feature Message-ID: <20161111225328.GB3142@twins.programming.kicks-ass.net> References: <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> <20161108195015.GP3117@twins.programming.kicks-ass.net> <8a80c2c2-3803-5648-67b2-4dee7381d5a6@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 852 Lines: 17 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.