public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: SCHED: Is task migration necessary in sched_exec().
Date: Wed, 23 Dec 2009 13:20:34 +0100	[thread overview]
Message-ID: <1261570834.4937.141.camel@laptop> (raw)
In-Reply-To: <b9df5fa10912230404p37edca22h54ef7dceec651de4@mail.gmail.com>

On Wed, 2009-12-23 at 18:04 +0600, Rakib Mullick wrote:
> On 12/23/09, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Wed, 2009-12-23 at 17:35 +0600, Rakib Mullick wrote:
> 
> >  Do you have a particular workload you worry about or are you merely
> >  trying to satisfy your curiosity?
> >
> No, I don't have any particular workload.

Anyway, look at it this way, suppose you have 4 tasks on 2 cpus, cpu0
has 3 tasks and cpu1 has 1 task.

The currently running task on cpu0 does exec and gets moved to cpu1,
even though it gives up time on cpu0, it gains time on cpu1. Because it
was eligible to 1/3 of cpu0's time, whereas it is eligible to 1/2 of
cpu1's time.

So its a win, right?



  reply	other threads:[~2009-12-23 12:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 10:14 SCHED: Is task migration necessary in sched_exec() Rakib Mullick
2009-12-23 10:21 ` Peter Zijlstra
2009-12-23 10:46   ` Rakib Mullick
2009-12-23 10:53     ` Peter Zijlstra
2009-12-23 11:35       ` Rakib Mullick
2009-12-23 11:51         ` Peter Zijlstra
2009-12-23 12:04           ` Rakib Mullick
2009-12-23 12:20             ` Peter Zijlstra [this message]
2009-12-23 12:52               ` Rakib Mullick
2009-12-23 18:06                 ` Peter Zijlstra
2009-12-25  2:53                   ` Rakib Mullick

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=1261570834.4937.141.camel@laptop \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rakib.mullick@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