mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Juri Lelli <juri.lelli@arm.com>
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
Date: Wed, 3 Feb 2016 13:10:41 -0500	[thread overview]
Message-ID: <20160203131041.3d5a3a97@gandalf.local.home> (raw)
In-Reply-To: <20160203175646.GD12132@e106622-lin>

On Wed, 3 Feb 2016 17:56:46 +0000
Juri Lelli <juri.lelli@arm.com> wrote:


> 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?

That's something I was planning on adding to that debugfs/sched
directory. But it may already be present. Perhaps it can be added to
the sched_debug file too if it isn't already there.

But that's a question for Peter.

-- Steve

  reply	other threads:[~2016-02-03 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 16:56 [RFC][PATCH 0/3 v2] sched: Display deadline bandwidth and other SCHED_DEBUG clean up Steven Rostedt
2016-02-03 16:56 ` [RFC][PATCH 1/3 v2] sched: Move sched_feature file setup into debug.c Steven Rostedt
2016-02-03 16:57 ` [RFC][PATCH 2/3 v2] sched: Move sched_domain_sysctl to debug.c Steven Rostedt
2016-02-03 16:57 ` [RFC][PATCH 3/3 v2] sched: Add bandwidth ratio to /proc/sched_debug Steven Rostedt
2016-02-03 17:56   ` Juri Lelli
2016-02-03 18:10     ` Steven Rostedt [this message]
2016-02-10 15:13 ` [RFC][PATCH 0/3 v2] sched: Display deadline bandwidth and other SCHED_DEBUG clean up Steven Rostedt

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=20160203131041.3d5a3a97@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=juri.lelli@arm.com \
    --cc=juri.lelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®