All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: Robert Love <rml@novell.com>
Cc: Ankit Jain <ankitjain1580@yahoo.com>,
	linux <linux-kernel@vger.kernel.org>
Subject: Re: processor affinity
Date: Tue, 28 Sep 2004 10:02:43 -0600	[thread overview]
Message-ID: <41598B23.50702@drdos.com> (raw)
In-Reply-To: <1096387088.4911.4.camel@betsy.boston.ximian.com>

Robert Love wrote:

>On Tue, 2004-09-28 at 08:04 -0600, Jeff V. Merkey wrote:
>
>  
>
>>Here's a real good description in a patent owned by Novell on the subject.
>>
>>Jeff
>>
>>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? :)
>
>	Robert Love
>
>  
>

I wrote them first, and coined the term. 

:-)

Jeff

>
>  
>


  reply	other threads:[~2004-09-28 16:36 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 [this message]
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
     [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=41598B23.50702@drdos.com \
    --to=jmerkey@drdos.com \
    --cc=ankitjain1580@yahoo.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 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.