From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dhaval Giani <dhaval@linux.vnet.ibm.com>,
randy.dunlap@oracle.com, mingo@elte.hu,
dmitry.adamushko@gmail.com, efault@gmx.de,
linux-kernel@vger.kernel.org, containers@lists.osdl.org
Subject: Re: [PATCH -mm] Hook up group scheduler with control groups
Date: Fri, 28 Sep 2007 08:10:26 +0530 [thread overview]
Message-ID: <20070928024026.GA1044@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070927164241.ca034043.akpm@linux-foundation.org>
On Thu, Sep 27, 2007 at 04:42:41PM -0700, Andrew Morton wrote:
> > @@ -219,6 +225,9 @@ static inline struct task_grp *task_grp(
> >
> > #ifdef CONFIG_FAIR_USER_SCHED
> > tg = p->user->tg;
> > +#elif CONFIG_FAIR_CGROUP_SCHED
> > + tg = container_of(task_subsys_state(p, cpu_cgroup_subsys_id),
> > + struct task_grp, css);
> > #else
> > tg = &init_task_grp;
> > #endif
>
> that's a bit funny-looking. Are CONFIG_FAIR_CGROUP_SCHED and
> CONFIG_FAIR_USER_SCHED mutually exclusive?
Yes. While configuring kernel, user can choose only one of those options
and not both.
> Doesn't seem that way.
Hmm ..why do you say that?
> if
> they're both defined then CONFIG_FAIR_USER_SCHED "wins".
> Anyway, please confirm that this is correct?
They can't both be defined.
> I'll switch that to `#elif defined(CONFIG_FAIR_CGROUP_SCHED)'. We can get
> gcc warnings with `#if CONFIG_FOO', and people should be using `#ifdef
> CONFIG_FOO', so I assume the same applies to #elif.
Thx for fixing it!
--
Regards,
vatsa
next prev parent reply other threads:[~2007-09-28 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 15:06 [PATCH -mm] Hook up group scheduler with control groups Srivatsa Vaddagiri
2007-09-27 17:40 ` Randy Dunlap
2007-09-27 18:04 ` Dhaval Giani
2007-09-27 19:00 ` Randy Dunlap
2007-09-27 19:35 ` Dhaval Giani
2007-09-27 23:42 ` Andrew Morton
2007-09-28 2:40 ` Srivatsa Vaddagiri [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-27 19:41 Frans Pop
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=20070928024026.GA1044@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=dmitry.adamushko@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.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