All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buffer <embuff@gmail.com>
To: netfilter@lists.netfilter.org
Subject: iptables on multiple CPUs (SMP & Hyperthreading question)
Date: Thu, 2 Jun 2005 17:21:36 -0500	[thread overview]
Message-ID: <d6dfb92c05060215211afa98c@mail.gmail.com> (raw)

I'm considering purchasing some firewall machines for my organization, and
I am trying to decide whether a machine with multiple CPUs is worth the
additional expense performance-wise (aside from being able to assign CPUs
to interfaces).  I'd also like to know whether there are any stability
issues with iptables & SMP (and/or hyperthreading with multiple CPUs).
Any input would be appreciated.

Thanks,
Michael


             reply	other threads:[~2005-06-02 22:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 22:21 Michael Buffer [this message]
2005-06-03  2:15 ` iptables on multiple CPUs (SMP & Hyperthreading question) /dev/rob0
2005-06-03 12:12   ` Sertys
2005-06-04 17:08 ` Mogens Valentin
  -- strict thread matches above, loose matches on Subject: below --
2005-06-03  4:05 Gary W. Smith

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=d6dfb92c05060215211afa98c@mail.gmail.com \
    --to=embuff@gmail.com \
    --cc=netfilter@lists.netfilter.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.