From: Mike Galbraith <efault@gmx.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: warning: (SCHED_AUTOGROUP) selects CGROUP_SCHED which has unmet direct dependencies (CGROUPS &&
Date: Tue, 02 Oct 2012 03:48:09 +0000 [thread overview]
Message-ID: <1349149689.7086.33.camel@marge.simpson.net> (raw)
In-Reply-To: <20121002025502.GA9385@localhost>
On Tue, 2012-10-02 at 10:55 +0800, Fengguang Wu wrote:
> Hi Mike,
>
> FYI, there are new compile warnings show up in
>
> commit: 5091faa449ee0b7d73bc296a93bca9540fc51d0a sched: Add 'autogroup' scheduling feature: automated per session task groups
> config: x86_64-randconfig-h011 (attached as .config)
Yeah, SCHED_AUTOGROUP should have also depended upon EXPERIMENTAL.
CGROUP_SCHED lost the EXPERIMENTAL dependency in 3.3. I don't think
this would qualify for a -stable backport, so there's not much I can do
about it now.
>
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -728,6 +728,19 @@ config NET_NS
>
> endif # NAMESPACES
>
> +config SCHED_AUTOGROUP
> + bool "Automatic process group scheduling"
> + select EVENTFD
> + select CGROUPS
> + select CGROUP_SCHED
> + select FAIR_GROUP_SCHED
> + help
> + This option optimizes the scheduler for common desktop workloads by
> + automatically creating and populating task groups. This separation
> + of workloads isolates aggressive CPU burners (like build jobs) from
> + desktop applications. Task group autogeneration is currently based
> + upon task session.
> +
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Centre
> Fengguang Wu, Yuanhan Liu Intel Corporation
prev parent reply other threads:[~2012-10-02 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 2:55 warning: (SCHED_AUTOGROUP) selects CGROUP_SCHED which has unmet direct dependencies (CGROUPS && EXPE Fengguang Wu
2012-10-02 3:48 ` Mike Galbraith [this message]
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=1349149689.7086.33.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=kernel-janitors@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox