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 12:51:52 +0100 [thread overview]
Message-ID: <1261569112.4937.135.camel@laptop> (raw)
In-Reply-To: <b9df5fa10912230335r459f86d4te868fca82b891752@mail.gmail.com>
On Wed, 2009-12-23 at 17:35 +0600, Rakib Mullick wrote:
> Yes - current heuristics does this - to make sure that it doesn't have to
> wait too long. It pushes process into another runqueue (probably less loaded)
> just to make sure that - it will get the CPU a bit quickly. But when a task
> got the CPU - we should keep it out of equation. The point of moving task
> is - it have to wait less. At exec current task don't have to wait to get CPU.
No, moving tasks isn't (primarily) about latency, it is about ensuring a
fair proportion of service time.
Do you have a particular workload you worry about or are you merely
trying to satisfy your curiosity?
next prev parent reply other threads:[~2009-12-23 11:52 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 [this message]
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=1261569112.4937.135.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.