From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,1d4203bfa2644439
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.180.87.165 with SMTP id az5mr969472wib.1.1355346718446;
        Wed, 12 Dec 2012 13:11:58 -0800 (PST)
Path: 
 i11ni140706wiw.0!nntp.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!195.96.0.7.MISMATCH!newsfeed.utanet.at!newsfeed.tele2net.at!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Jeffrey Carter <spam.jrcarter.not@spam.not.acm.org>
Newsgroups: comp.lang.ada
Subject: Re: Task with access to itself?
Date: Wed, 12 Dec 2012 14:11:56 -0700
Organization: Also freenews.netfront.net; news.tornevall.net
Message-ID: <kaarus$die$1@dont-email.me>
References: <8738zk7gge.fsf@adaheads.sparre-andersen.dk>
 <k9nuct$f4n$1@dont-email.me> <87ehiwygv1.fsf@adaheads.sparre-andersen.dk>
 <ka85lk$8pe$1@dont-email.me> <87k3snj9wc.fsf@adaheads.sparre-andersen.dk>
Mime-Version: 1.0
Injection-Date: Wed, 12 Dec 2012 21:11:58 +0000 (UTC)
Injection-Info: mx04.eternal-september.org;
 posting-host="21c3f140f3af3f178681f105ae93b5ae";
	logging-data="13902"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19/E7MexorwmjnXaM7Ulnd281WgQz2Jmzk="
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/17.0 Thunderbird/17.0
In-Reply-To: <87k3snj9wc.fsf@adaheads.sparre-andersen.dk>
Cancel-Lock: sha1:fvmafrYGaSOYvoEg2Vs660dMn9k=
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: 2012-12-12T14:11:56-07:00
List-Id: <comp.lang.ada>

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