From: Rakib Mullick <rakib.mullick@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
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 16:46:31 +0600 [thread overview]
Message-ID: <b9df5fa10912230246w4adf160bibc12d7c6480ce058@mail.gmail.com> (raw)
In-Reply-To: <1261563687.4937.120.camel@laptop>
On 12/23/09, Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, 2009-12-23 at 16:14 +0600, Rakib Mullick wrote:
>
>
> 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.
>
If there is an imbalance - then the overloaded task will moved. Why the
_current_ task? It is getting the CPU that it was waiting for. We need to
move overloaded task, not a task which is about to get execute. At this
perticular moment pushing it away doesn't make sense, isn't it?
> So moving it when its cheapest is the best all-round trade-off, isn't
> it?
I don't have any argue with cache footprint issue.
>
>
thanks,
next prev parent reply other threads:[~2009-12-23 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 10:14 Rakib Mullick
2009-12-23 10:21 ` Peter Zijlstra
2009-12-23 10:46 ` Rakib Mullick [this message]
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=b9df5fa10912230246w4adf160bibc12d7c6480ce058@mail.gmail.com \
--to=rakib.mullick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/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®