From: Fran Fabrizio <fran@cis.uab.edu>
To: netfilter@lists.netfilter.org
Subject: Any advantage of multicore for netfilter/iptables?
Date: Thu, 14 Jun 2007 14:36:59 -0500 [thread overview]
Message-ID: <467198DB.7080107@cis.uab.edu> (raw)
I am configuring a new router/firewall. I'm making the hardware
purchase and I need to decide what processor(s) I want.
My thought process went thusly: netfilter/iptables is part of the
kernel, the kernel is threaded, so does this imply that on a multicore
machine it is in theory possible that iptables might use a different
core to examine each packet, and if so, is there any possibility for
concurrency or is it strictly linear? I'm -real- fuzzy on how the
kernel does its threading in relation to modules and specifically the
netfilter hooks (as made obvious by me asking this).
The practical question is that if you were setting up a router/firewall
server right now, would you prefer a slower clock speed but more cores,
or the fastest individual core speed, all other things being equal?
A valid related question is, does it even matter or would any modern
processor and server be able to easily inspect traffic on a 1Gbit link
with iptables without breaking a sweat? This will be a Dell PowerEdge
1950 server with Xeon dual or quad core, I plan to use Intel Pro server
NICs, either 2 or 4 port PCIe cards.
Would appreciate any feedback you folks might have.
Thanks,
Fran
--
Fran Fabrizio
Senior Systems Analyst
Department of Computer and Information Sciences
University of Alabama at Birmingham
http://www.cis.uab.edu/
205.934.0653
reply other threads:[~2007-06-14 19:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=467198DB.7080107@cis.uab.edu \
--to=fran@cis.uab.edu \
--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.