From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
Balbir Singh <balbir@in.ibm.com>,
Aneesh Kumar KV <aneesh.kumar@linux.vnet.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
vgoyal@redhat.com, serue@us.ibm.com, menage@google.com
Subject: Re: [RFC, PATCH 1/2] sched: change the fairness model of the CFS group scheduler
Date: Tue, 4 Mar 2008 15:19:44 +0530 [thread overview]
Message-ID: <20080304094944.GB3730@linux.vnet.ibm.com> (raw)
In-Reply-To: <1204281475.6243.73.camel@lappy>
On Fri, Feb 29, 2008 at 11:37:55AM +0100, Peter Zijlstra wrote:
>
> On Fri, 2008-02-29 at 14:34 +0530, Dhaval Giani wrote:
>
> > > > +#elif defined CONFIG_USER_SCHED
> > > > + /*
> > > > + * In case of task-groups formed thr' the user id of tasks,
> > > > + * init_task_group represents tasks belonging to root user.
> > > > + * Hence it forms a sibling of all subsequent groups formed.
> > > > + * In this case, init_task_group gets only a fraction of overall
> > > > + * system cpu resource, based on the weight assigned to root
> > > > + * user's cpu share (INIT_TASK_GROUP_LOAD). This is accomplished
> > > > + * by letting tasks of init_task_group sit in a separate cfs_rq
> > > > + * (init_cfs_rq) and having one entity represent this group of
> > > > + * tasks in rq->cfs (i.e init_task_group->se[] != NULL).
> > > > + */
> > > > init_tg_cfs_entry(rq, &init_task_group,
> > > > &per_cpu(init_cfs_rq, i),
> > > > &per_cpu(init_sched_entity, i), i, 1);
> > >
> > > But I fail to parse this lengthy comment. What does it do:
> > >
> > > init_group
> > > / | \
> > > uid-0 uid-1000 uid-n
> > >
> > > or does it blend uid-0 into the init_group?
> > >
> >
> > It blends uid-0 (root) into init_group.
>
> Any particular reason why? It seems to me uid-0 should be treated like
> any other uid.
>
Ah, I misunderstood your question. We have not changed anything for UID
scheduling as no task can (should) exist at the root level (init_group).
Your initial figure is right, sorry for the confusion.
Thanks,
--
regards,
Dhaval
next prev parent reply other threads:[~2008-03-04 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 14:15 [RFC, PATCH 0/2] sched: add multiple hierarchy support to the CFS group scheduler Dhaval Giani
2008-02-25 14:16 ` [RFC, PATCH 1/2] sched: change the fairness model of " Dhaval Giani
2008-02-27 20:23 ` Serge E. Hallyn
2008-02-28 19:42 ` Peter Zijlstra
2008-02-29 9:04 ` Dhaval Giani
2008-02-29 10:37 ` Peter Zijlstra
2008-03-04 9:49 ` Dhaval Giani [this message]
2008-02-25 14:17 ` [RFC, PATCH 1/2] sched: allow the CFS group scheduler to have multiple levels Dhaval Giani
2008-02-25 14:17 ` Dhaval Giani
2008-02-28 19:42 ` Peter Zijlstra
2008-02-29 5:57 ` Dhaval Giani
-- strict thread matches above, loose matches on Subject: below --
2008-02-29 0:43 [RFC, PATCH 1/2] sched: change the fairness model of the CFS group scheduler J.C. Pizarro
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=20080304094944.GB3730@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=serue@us.ibm.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=vgoyal@redhat.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