All of lore.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 11:21:27 +0100	[thread overview]
Message-ID: <1261563687.4937.120.camel@laptop> (raw)
In-Reply-To: <b9df5fa10912230214s3815c023g2a7e7ca152eb00e4@mail.gmail.com>

On Wed, 2009-12-23 at 16:14 +0600, Rakib Mullick wrote:
> Is task migration necessary in sched_exec()?
> 
>  In sched_exec function's comment it says:
> 
>  "sched_exec - execve() is a valuable balancing opportunity, because at
>   this point the task has the smallest effective memory and cache footprint."
> 
> Right, but - when a execve() is called then this task will start execution (that
> means this task will not waiting on the runqueue as TASK_RUNNING/WAKING,
> it will get the CPU). At this point - what is the necessity to try
> making it balance.
> By looking at point of "smallest effective memory and cache footprint" , we are
> missing the point that we are unnecessarily pushing task when its
> about to execute.
> 
> Isn't it? Or I'm missing anything?

Well, if there's an imbalance the 'slow' load-balancer will move it
around eventually anyway, and since it will then have build up a larger
cache footprint it will be even more expensive.

So moving it when its cheapest is the best all-round trade-off, isn't
it?


  reply	other threads:[~2009-12-23 10:22 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 [this message]
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
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=1261563687.4937.120.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.