From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <efault@gmx.de>
Cc: David Ahern <david.ahern@oracle.com>,
mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched: Add cpu based entries to debugfs
Date: Mon, 30 Mar 2015 10:28:12 +0200 [thread overview]
Message-ID: <20150330082812.GP23123@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1427703963.7560.3.camel@gmx.de>
On Mon, Mar 30, 2015 at 10:26:03AM +0200, Mike Galbraith wrote:
> On Mon, 2015-03-30 at 09:44 +0200, Peter Zijlstra wrote:
> > On Sun, Mar 29, 2015 at 10:13:33PM -0400, David Ahern wrote:
> > > Before spending too much time formalizing this I wanted to see if you guys
> > > would entertain the idea of making this info available via debugfs. It does
> > > move the existing sched_features file to sched/features -- not sure how
> > > acceptable it is to move files in debugfs.
> >
> > There also already is a /proc/sys/kernel/sched_domain/ sysctl thing that
> > has much of the stuff in.
> >
> > I'm not opposed to a debugfs thing, but only if we can take the sysctl
> > thing out.
>
> Ew, I can see the regression reports now. That stuff has long roots.
I didn't say we could take it out, I only said it would maybe be nice to
be able to :-) But yah. It'll cause some pain if we do :/
next prev parent reply other threads:[~2015-03-30 8:28 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
2015-03-30 7:44 ` Peter Zijlstra
2015-03-30 8:26 ` Mike Galbraith
2015-03-30 8:28 ` Peter Zijlstra [this message]
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=20150330082812.GP23123@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=david.ahern@oracle.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.