All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SMP in regards to routing/filtering
Date: Sat, 31 Aug 2002 11:55:18 +0000	[thread overview]
Message-ID: <marc-lartc-103079499307407@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103076253625864@msgid-missing>

On Fri, Aug 30, 2002 at 10:11:46PM -0500, Phil Doroff wrote:
> Hey, quick (stupid) question..
> 
> 	Is the routing/filtering code in the linux kernel able to take much
> advantage of SMP?  I'm building a router that I'd like to be able to handle
> at least 450mbit/sec (64bit 66mhtz PCI slots of course) and be able to apply
> QoS (basic prio queues) and htb/etc. traffic shaping to.

Under some circumstances, a second CPU can be very useful. It depends on
what you are doing, but the Linux networking core is completely able to
paralelly use processors. 

You may need to do some work to give each network adaptor a dedicated CPU
and you will also want to have multiple PCI busses.

> Just wondering if it's worth grabbing an extra processor for the box, or if
> it will largely go unused.

It will see use but if you mess things up, it will not help. So make sure
that you search on 'irq affinity' and the utility of multiple PCI busses.
Perhaps a 64-bit 66MHz bus is fast enough to get by with one.

Regards,

bert hubert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-08-31 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-31  2:55 [LARTC] SMP in regards to routing/filtering Phil Doroff
2002-08-31 11:55 ` bert hubert [this message]
2002-09-03 14:11 ` David Boreham

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=marc-lartc-103079499307407@msgid-missing \
    --to=ahu@ds9a.nl \
    --cc=lartc@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 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.