public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
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: Wed, 29 Sep 2004 18:45:10 +0100	[thread overview]
Message-ID: <20040929184510.A15692@infradead.org> (raw)
In-Reply-To: <415AE953.3070105@drdos.com>; from jmerkey@drdos.com on Wed, Sep 29, 2004 at 10:56:51AM -0600

On Wed, Sep 29, 2004 at 10:56:51AM -0600, Jeff V. Merkey wrote:
> 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.  This implementation (like 
> Linux) was specific to IA32 architecture systems. 

The Linux implementation works on about a dozen plattforms, or how
many smp ports we have these days..


  reply	other threads:[~2004-09-29 17:45 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 [this message]
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=20040929184510.A15692@infradead.org \
    --to=hch@infradead.org \
    --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