mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: joe briggs <jbriggs@briggsmedia.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: impact of Athlon's slower front-side-bus (FSB)
Date: 02 Jun 2003 15:47:40 +0100	[thread overview]
Message-ID: <1054565258.7494.34.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200306020947.44520.jbriggs@briggsmedia.com>

On Llu, 2003-06-02 at 14:47, joe briggs wrote:
> The fastest AMD single processor Athlon XP is 3200 with 400 Mhz FSB.
> The fastest AMD dual processor Athlon MP is 2800 but with only 266 Mhz FSB.
> 
> So, for a multimedia application, which platform would be faster?  How does 
> the much slower FSB of the dual processor impact its ability to grab and 
> crunch.  Does its onboard cache make the slower speed FSB less important?  

Its really hard to tell. The 3200 has a bigger cache too if I remember
rightly. If you are planning on buying big boxes for this you might want
to ask the vendor if you can do a test run or two.

> Also, does a dual processor platform distribute the interrupt loading as well 
> as process loading?  I my systems I have between 1 and 8 frame identical 
> frame grabbers.  Would the interrupt processing of these devices be 
> distributed evenly on the dual processor platforms?

Yes. You would probably want to tie different cards/encoders to
different processors and the IRQ to the same one. You can do this via
/proc and with the -ac or most vendor trees (and 2.5) you can tie
processes to CPUs with syscalls


  reply	other threads:[~2003-06-02 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 13:47 joe briggs
2003-06-02 14:47 ` Alan Cox [this message]
2003-06-02 18:36   ` joe briggs
2003-06-02 19:14     ` Doug McNaught
2003-06-04 17:15   ` OT: " William Gallafent

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=1054565258.7494.34.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jbriggs@briggsmedia.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®