mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: vatsa@linux.vnet.ibm.com
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	ckrm-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	containers@lists.osdl.org,
	"Jan Engelhardt" <jengelh@computergmbh.de>,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: [PATCH] Hookup group-scheduler with task container infrastructure
Date: Tue, 11 Sep 2007 00:28:51 +0200	[thread overview]
Message-ID: <b647ffbd0709101528i7440a0f9m9837065a43e4a720@mail.gmail.com> (raw)
In-Reply-To: <20070910174649.GA16222@linux.vnet.ibm.com>

On 10/09/2007, Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:
> On Mon, Sep 10, 2007 at 10:22:59AM -0700, Andrew Morton wrote:
> > objection ;)  "cpuctlr" isn't memorable.  Kernel code is write-rarely,
> > read-often.  "cpu_controller", please.  The extra typing is worth it ;)
>
> Ok! Here's the modified patch (against 2.6.23-rc4-mm1).
>
> [ ... ]
>
> +/* change task's runqueue when it moves between groups */
> +static void sched_move_task(struct container_subsys *ss, struct container *cont,
> +                       struct container *old_cont, struct task_struct *tsk)
> +{
> +       int on_rq;
> +       unsigned long flags;
> +       struct rq *rq;
> +
> +       rq = task_rq_lock(tsk, &flags);
> +

I guess, update_rq_clock(rq) should be placed here.

humm... do you really need deactivate/activate_task() here? 'rq' and
p->se.load.weight stay unchanged so enqueue/dequeue_task() would do a
job, no?
Although, I might be missing (definitely, as this part is not
completely clear to me yet) something important at this late hour :)


> +       on_rq = tsk->se.on_rq;
> +       if (on_rq)
> +               deactivate_task(rq, tsk, 0);
> +
> +       if (unlikely(rq->curr == tsk) && tsk->sched_class == &fair_sched_class)
> +               tsk->sched_class->put_prev_task(rq, tsk);
> +
> +       set_task_cfs_rq(tsk);
> +
> +       if (on_rq)
> +                activate_task(rq, tsk, 0);
> +
> +       if (unlikely(rq->curr == tsk) && tsk->sched_class == &fair_sched_class)
> +               tsk->sched_class->set_curr_task(rq);
> +
> +       task_rq_unlock(rq, &flags);
> +}
> +


-- 
Best regards,
Dmitry Adamushko

  reply	other threads:[~2007-09-10 22:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10 17:10 Srivatsa Vaddagiri
2007-09-10 17:05 ` Jan Engelhardt
2007-09-10 17:23   ` Srivatsa Vaddagiri
2007-09-10 17:22     ` Andrew Morton
2007-09-10 17:41       ` Jan Engelhardt
2007-09-10 17:46       ` Srivatsa Vaddagiri
2007-09-10 22:28         ` Dmitry Adamushko [this message]
2007-09-11  4:41           ` Srivatsa Vaddagiri
2007-09-11  9:53             ` Dmitry Adamushko
2007-09-12 11:42               ` Srivatsa Vaddagiri
2007-09-12 12:10                 ` Srivatsa Vaddagiri
2007-09-12 16:25                 ` Dmitry Adamushko
2007-09-13 12:33                   ` Srivatsa Vaddagiri
2007-09-14  9:41                     ` Ingo Molnar
2007-09-14 15:59                       ` Srivatsa Vaddagiri
2007-09-14 16:22                         ` Srivatsa Vaddagiri
2007-09-10 22:37         ` Dmitry Adamushko
2007-09-10 22:45           ` Paul Menage
2007-09-11  7:20             ` Cedric Le Goater
2007-09-11 15:22               ` Randy Dunlap
2007-09-11 15:37                 ` Jan Engelhardt
2007-09-11 15:51                 ` Srivatsa Vaddagiri
2007-09-11 15:53                   ` Randy Dunlap
2007-09-11 15:44               ` Paul Menage
2007-09-10 17:28     ` Srivatsa Vaddagiri
2007-09-10 17:42       ` Jan Engelhardt
2007-09-10 18:38     ` [Devel] " Paul Menage
2007-09-11  4:44       ` Srivatsa Vaddagiri
2007-09-18  8:19 ` KAMEZAWA Hiroyuki
2007-09-18 10:44   ` Srivatsa Vaddagiri

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=b647ffbd0709101528i7440a0f9m9837065a43e4a720@mail.gmail.com \
    --to=dmitry.adamushko@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=containers@lists.osdl.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vatsa@linux.vnet.ibm.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®