From: Mike Galbraith <efault@gmx.de>
To: Xiaotian Feng <xtfeng@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Xiaotian Feng <dannyfeng@tencent.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] V2 sched, autogroup: fix crash on reboot when autogroup is disabled
Date: Mon, 29 Oct 2012 05:10:15 -0700 [thread overview]
Message-ID: <1351512615.9785.25.camel@maggy.simpson.net> (raw)
In-Reply-To: <CAJn8CcFO9BB7yfoo2158FPV75Za7yoYqrf_KfwPdA-AdkT=Qsw@mail.gmail.com>
On Mon, 2012-10-29 at 10:42 +0800, Xiaotian Feng wrote:
> I'm okay with the removal of runtime enable/disable autogroup. But can
> we simply remove
> these two knobs that is already exposed to user space since 2.6.38 ?
> So we can't cat /proc/<pid>/autogroup
> or echo <nice level> > /proc/<pid>/autogroup anymore even if autogroup is on?
I should have never made those knobs, as it's against the whole idea of
automatic no muss no fuss group scheduling. If you want knobs, you want
full cgroups, so I think we should call this a fix opportunity.
If the knobs are seen as being cast in stone, I'll do the full move for
the on/off switch instead, and there will be no user visible change. I'd
rather not do that. This way, it's really out of the way when disabled,
smaller and simpler is better for this feature.
It's a dinky little sidelines feature, so let's just quietly make kaboom
go away, non-functional on/off go away, along with the silly knobs which
will make kaboom unless you jump through hoops just to keep them alive.
-Mike
next prev parent reply other threads:[~2012-10-29 12:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 8:36 [PATCH] sched, autogroup: fix kernel crashes caused by runtime disable autogroup Xiaotian Feng
2012-10-19 13:42 ` Peter Zijlstra
2012-10-20 6:42 ` Xiaotian Feng
2012-10-20 12:38 ` Mike Galbraith
2012-10-26 20:29 ` Mike Galbraith
2012-10-27 18:26 ` [PATCH] sched, autogroup: fix crash on reboot when autogroup is disabled Mike Galbraith
2012-10-28 10:25 ` Ingo Molnar
2012-10-28 13:13 ` Mike Galbraith
2012-10-28 13:19 ` Ingo Molnar
2012-10-28 13:33 ` Mike Galbraith
2012-10-28 14:05 ` Ingo Molnar
2012-10-28 14:27 ` Mike Galbraith
2012-10-28 19:19 ` [PATCH] V2 " Mike Galbraith
2012-10-29 2:42 ` Xiaotian Feng
2012-10-29 12:10 ` Mike Galbraith [this message]
2012-10-30 12:28 ` [tip:sched/urgent] sched/autogroup: Fix " tip-bot for Mike Galbraith
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=1351512615.9785.25.camel@maggy.simpson.net \
--to=efault@gmx.de \
--cc=dannyfeng@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=xtfeng@gmail.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®