From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751818AbcBWJyr (ORCPT ); Tue, 23 Feb 2016 04:54:47 -0500 Received: from foss.arm.com ([217.140.101.70]:35509 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750918AbcBWJyp (ORCPT ); Tue, 23 Feb 2016 04:54:45 -0500 Date: Tue, 23 Feb 2016 09:55:42 +0000 From: Juri Lelli To: Steven Rostedt Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Peter Zijlstra , Thomas Gleixner , Juri Lelli , Clark Williams , Andrew Morton Subject: Re: [PATCH 3/4] sched: Add bandwidth ratio to /proc/sched_debug Message-ID: <20160223095542.GH27380@e106622-lin> References: <20160222212649.485719441@goodmis.org> <20160222212825.756849091@goodmis.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160222212825.756849091@goodmis.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Steve, On 22/02/16 16:26, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > Playing with SCHED_DEADLINE and cpusets, I found that I was unable to create > new SCHED_DEADLINE tasks, with the error of EBUSY as if the bandwidth was > already used up. I then realized there wa no way to see what bandwidth is > used by the runqueues to debug the issue. > > By adding the dl_bw->bw and dl_bw->total_bw to the output of the deadline > info in /proc/sched_debug, this allows us to see what bandwidth has been > reserved and where a problem may exist. > [...] > > Signed-off-by: Steven Rostedt This is pretty useful yes. FWIW, Acked-by: Juri Lelli Best, - Juri