From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Jeff V. Merkey" <jmerkey@drdos.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Robert Love <rml@novell.com>,
Ankit Jain <ankitjain1580@yahoo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: processor affinity
Date: Thu, 30 Sep 2004 12:39:12 +1000 [thread overview]
Message-ID: <415B71D0.3020100@yahoo.com.au> (raw)
In-Reply-To: <415AE953.3070105@drdos.com>
Jeff V. Merkey wrote:
> Alan Cox wrote:
>
>> On Maw, 2004-09-28 at 17:02, Jeff V. Merkey wrote:
>>
>>
>>>>> http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=/netahtml/search-bool.html&r=2&f=G&l=50&co1=AND&d=ptxt&s1=merkey.INZZ.&OS=IN/merkey&RS=IN/merkey
>>>>>
>>>>>
>>>>
>>>> Wow, I never knew about that.
>>>>
>>>> But guess who wrote the affinity system calls? :)
>>>>
>>
>>
>>
>>
>>> I wrote them first, and coined the term.
>>
>>
>> Cute but GCOS3 had affinity syscalls for batch processing in the 1970's
>> and I don't believe it was original even then.
>>
>>
>
> Using them for Intel Cache affinity was new at the time. Intel SMP
> hardware was not readily available at the time and was in
> its infancy in 1993 when this was developed.
That is amazingly specific - I suppose using it for cache affinity on
earlier processors wouldn't count :)
Joking aside, this doesn't seem like it would apply to Linux's scheduler.
We don't use a global queue, and we don't implement hard affinities with
local queues, but with a specific bitmask of cpus.
Of course, I don't really have any idea how to interpret patents...
next prev parent reply other threads:[~2004-09-30 2:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 12:25 processor affinity Ankit Jain
2004-09-28 13:39 ` Toon van der Pas
2004-09-28 13:47 ` Jon Masters
2004-09-28 13:55 ` Neil Horman
2004-09-28 14:04 ` Jeff V. Merkey
2004-09-28 15:58 ` Robert Love
2004-09-28 16:02 ` Jeff V. Merkey
2004-09-28 21:51 ` Alan Cox
2004-09-29 16:56 ` Jeff V. Merkey
2004-09-29 17:45 ` Christoph Hellwig
2004-09-29 19:24 ` Jeff V. Merkey
2004-09-29 20:08 ` Jon Masters
2004-09-29 19:43 ` Jeff V. Merkey
2004-09-29 20:28 ` Jon Masters
2004-09-29 20:03 ` Jeff V. Merkey
2004-09-30 2:39 ` Nick Piggin [this message]
[not found] ` <20040930124708.GA2520@galt.devicelogics.com>
2004-10-01 3:09 ` Nick Piggin
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=415B71D0.3020100@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ankitjain1580@yahoo.com \
--cc=jmerkey@drdos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox