From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mike Galbraith <efault@gmx.de>,
David Ahern <david.ahern@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched: Add cpu based entries to debugfs
Date: Tue, 31 Mar 2015 11:13:24 +0200 [thread overview]
Message-ID: <20150331091324.GA16810@gmail.com> (raw)
In-Reply-To: <20150330091841.GR23123@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Mar 30, 2015 at 10:43:14AM +0200, Mike Galbraith wrote:
>
> > I think it would be a good thing if we can get away with it, but I
> > also think you could safely bet your life that somebody will
> > squeak.
>
> The thing I worry most about is that squeaking only happening 5
> years later :/
So lets start by keeping the sysctl thing with the very
scheduler-internal names, but all zeroes and no effect of any change -
i.e. a dead API in all but appearance. I don't think there's any
legitimate use of those, beyond debugging, as we could change the
internal implementation anymore and moot many of those flags.
So lets trigger the squeaking that way. If any complaint comes in
beyond 1-2 kernel releases then I don't think it's a regression, it
turns into a feature request ...
Thanks,
Ingo
next prev parent reply other threads:[~2015-03-31 9:13 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
2015-03-30 8:43 ` Mike Galbraith
2015-03-30 9:18 ` Peter Zijlstra
2015-03-31 9:13 ` Ingo Molnar [this message]
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=20150331091324.GA16810@gmail.com \
--to=mingo@kernel.org \
--cc=david.ahern@oracle.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.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