From: Jeffrey Carter <spam.jrcarter.not@spam.not.acm.org>
Subject: Re: Task with access to itself?
Date: Wed, 12 Dec 2012 14:11:56 -0700
Date: 2012-12-12T14:11:56-07:00 [thread overview]
Message-ID: <kaarus$die$1@dont-email.me> (raw)
In-Reply-To: <87k3snj9wc.fsf@adaheads.sparre-andersen.dk>
On 12/12/2012 01:25 PM, Jacob Sparre Andersen wrote:
>
> Because I prefer to activate the most recently used task first, as it is
> likely to be the one which is "closest" to a CPU (i.e. least likely to
> be swapped out to disk).
You're not talking about activation; you're talking about which task handles the
next job. Our scheme does the opposite of what you want; the task that handles
the next job is usually the one that has been idle the longest.
--
Jeff Carter
"I unclog my nose towards you."
Monty Python & the Holy Grail
11
next prev parent reply other threads:[~2012-12-12 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 13:53 Task with access to itself? Jacob Sparre Andersen
2012-12-05 14:18 ` Dmitry A. Kazakov
2012-12-05 16:57 ` Jeffrey Carter
2012-12-11 11:21 ` Jacob Sparre Andersen
2012-12-11 20:39 ` Jeffrey Carter
2012-12-12 20:25 ` Jacob Sparre Andersen
2012-12-12 21:11 ` Jeffrey Carter [this message]
2012-12-13 7:20 ` Jacob Sparre Andersen
2012-12-06 9:38 ` Egil Høvik
2012-12-06 19:53 ` Adam Beneschan
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox