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 S965110AbcBCR4H (ORCPT <rfc822;w@1wt.eu>);
	Wed, 3 Feb 2016 12:56:07 -0500
Received: from foss.arm.com ([217.140.101.70]:36140 "EHLO foss.arm.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S964787AbcBCR4F (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 3 Feb 2016 12:56:05 -0500
Date: Wed, 3 Feb 2016 17:56:46 +0000
From: Juri Lelli <juri.lelli@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Juri Lelli <juri.lelli@gmail.com>,
        Clark Williams <williams@redhat.com>,
        Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH 3/3 v2] sched: Add bandwidth ratio to
 /proc/sched_debug
Message-ID: <20160203175646.GD12132@e106622-lin>
References: <20160203165658.910282657@goodmis.org>
 <20160203165955.184691855@goodmis.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160203165955.184691855@goodmis.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi,

On 03/02/16 11:57, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
> 
> 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.
> 
> For example, before the issue we see the ratio of the bandwidth:
> 
>  # cat /proc/sys/kernel/sched_rt_runtime_us
>  950000
>  # cat /proc/sys/kernel/sched_rt_period_us
>  1000000
> 
>   # grep dl /proc/sched_debug
>   dl_rq[0]:
>     .dl_nr_running                 : 0
>     .dl_bw->bw                     : 996147
>     .dl_bw->total_bw               : 0
>   dl_rq[1]:
>     .dl_nr_running                 : 0
>     .dl_bw->bw                     : 996147
>     .dl_bw->total_bw               : 0
>   dl_rq[2]:
>     .dl_nr_running                 : 0
>     .dl_bw->bw                     : 996147
>     .dl_bw->total_bw               : 0
>   dl_rq[3]:
>     .dl_nr_running                 : 0
>     .dl_bw->bw                     : 996147
>     .dl_bw->total_bw               : 0
>   dl_rq[4]:
>     .dl_nr_running                 : 0
>     .dl_bw->bw                     : 996147
>     .dl_bw->total_bw               : 0
>   dl_rq[5]:
>     .dl_nr_running                 : 0
>     .dl_bw->bw                     : 996147
>     .dl_bw->total_bw               : 0
>   dl_rq[6]:
>     .dl_nr_running                 : 0
>     .dl_bw->bw                     : 996147
>     .dl_bw->total_bw               : 0
>   dl_rq[7]:
>     .dl_nr_running                 : 0
>     .dl_bw->bw                     : 996147
>     .dl_bw->total_bw               : 0
>

I think this is already quite useful. But, do you think we can also
display information about the root_domain (like the span for example)?
Or do we have that some place else already?

Thanks,

- Juri