public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: "Martin A. Brooks" <martin@jtrix.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: asynchronus multiprocessing
Date: Thu, 20 Dec 2001 14:15:52 -0800	[thread overview]
Message-ID: <3C226318.4D2EBC9E@mvista.com> (raw)
In-Reply-To: <1008776432.431.15.camel@unhygienix> <1008777560.431.19.camel@unhygienix>  <3C20D9DC.B14709FD@mvista.com> <1008834258.431.21.camel@unhygienix>

"Martin A. Brooks" wrote:
> 
> On Wed, 2001-12-19 at 18:18, george anzinger wrote:
> 
> > I have heard of some work.  As I understand it they are making an API
> > for cpu affinity.  It is real time, so they are also interested in the
> > schedule routines around cpu affinity as well.
> >
> > What did you have in mind?
> 
> Nothing too major, I just intend to buy myself a dual Athlon. I would
> rather recycle my perfectly good 1.3ghz chip and use it in conjuction
> with a 1.5ghz athlon rather than buying two new processors.
> 
Apart from the clock differences (which if actually presented to the two
cpus would cause the TSC to drift apart cause who knows what mayhem)
what is the real difference?  I think you would have to make sure you
configure for the subset of chip capabilities so you don't find the
system trying to use some capability that is only present on one cpu and
then switching the ap to the other.  As I recall, someone has already
explored this turf to some extent.  Check the archives.

But really, I was wondering what you thought needed to be done in
software?
-- 
George           george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/

      reply	other threads:[~2001-12-20 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 15:40 asynchronus multiprocessing Martin A. Brooks
2001-12-19 15:59 ` Martin A. Brooks
2001-12-19 18:09   ` John Clemens
2001-12-19 18:18   ` george anzinger
2001-12-20  7:44     ` Martin A. Brooks
2001-12-20 22:15       ` george anzinger [this message]

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=3C226318.4D2EBC9E@mvista.com \
    --to=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@jtrix.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