From: Jacob Sparre Andersen <sparre@nbi.dk>
Subject: Re: Task with access to itself?
Date: Thu, 13 Dec 2012 08:20:05 +0100
Date: 2012-12-13T08:20:05+01:00 [thread overview]
Message-ID: <878v921kre.fsf@adaheads.sparre-andersen.dk> (raw)
In-Reply-To: kaarus$die$1@dont-email.me
Jeffrey Carter wrote:
> 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;
No, not in the Ada sense of the term. Sorry for the confusion.
> 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.
That is also what I would expect from a "typical" Ada run-time.
Greetings,
Jacob
--
"The universe isn't for the likes of me to understand. I only work here."
next prev parent reply other threads:[~2012-12-13 7:20 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
2012-12-13 7:20 ` Jacob Sparre Andersen [this message]
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