public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: David Ahern <david.ahern@oracle.com>
Cc: peterz@infradead.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched: Add cpu based entries to debugfs
Date: Mon, 30 Mar 2015 16:45:49 +0200	[thread overview]
Message-ID: <1427726749.7560.26.camel@gmx.de> (raw)
In-Reply-To: <55194999.9090007@oracle.com>

On Mon, 2015-03-30 at 07:03 -0600, David Ahern wrote:
> On 3/29/15 9:08 PM, Mike Galbraith wrote:
> >
> > Oh, you can add /proc/sys/kernel/sched_domain diddling to the hotplug
> > todo... which will either create read /sys, poke modify buttons over
> > yonder in /proc situation, or have to duplicate that.
> 
> -EPARSE.
> 
> you mean the /proc/sys/kernel/sched_domain/ files do not handle hotplug?
> 
> Can I get --verbose on what you mean above?

I meant hotplug isn't the only thing that alters what you display, and
the display is disjointed from the knobs, user acquires pretty display
in /sys, but the knobs to twiddle what he's looking at are elsewhere.

	-Mike


  reply	other threads:[~2015-03-30 14:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30  2:13 [RFC PATCH] sched: Add cpu based entries to debugfs David Ahern
2015-03-30  2:32 ` Mike Galbraith
2015-03-30  2:48   ` David Ahern
2015-03-30  3:08     ` Mike Galbraith
2015-03-30 13:03       ` David Ahern
2015-03-30 14:45         ` Mike Galbraith [this message]
2015-03-30  7:44 ` Peter Zijlstra
2015-03-30  8:26   ` Mike Galbraith
2015-03-30  8:28     ` Peter Zijlstra
2015-03-30  8:43       ` Mike Galbraith
2015-03-30  9:18         ` Peter Zijlstra
2015-03-31  9:13           ` Ingo Molnar
2015-04-06  2:10             ` David Ahern
2015-04-06  4:04               ` Mike Galbraith
2015-03-30 13:02   ` David Ahern

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=1427726749.7560.26.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=david.ahern@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    /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