I like multicore / multicpu amd opteron boards from Tyan. With a dual
core (later you can double to 4 core) dual cpu motherboard, you can
route and shape to your hearts content. To really improve throughput,
you should use a higher end network controller with pci-express with
some smarts and
Derek Sims wrote:
Marek Kierdelewicz wrote
1. What processors should I be looking for in order to achieve the
best routing throughput on a linux router?
I've had good experiences with P4 (with and without HT), Athlon64, Xeon
[dempsey], Xeon [woodcrest]. The last one is the best choice beca
Derek Sims wrote:
Marek Kierdelewicz wrote:
Hmm - I don't know what the "set" module is - can you point me to some
documentation please?
Search for ipset extensions for iptables or look up extension projects
in netfilter.org.
ipset gives the facility to create sets of IPs and use the sets in
>Hi
Hi
>is there any how-to which can guide me through all available tuning
>options in /proc/ filesystem
Proc filesystem is described in file Documentation/filesystems/proc.txt
in the linux kernel sources. You can find there something about
smp_affinity and linux network stack parameters (and
Hi
is there any how-to which can guide me through all available tuning options
in /proc/ filesystem
Pozdrawiam
Szymon Turkiewicz
> >Hi
>
> Hi
>
> >I have a router with a large number of iptables rules and some
> >extensive traffic shaping (HTB + RED + ... ) + conntrack.
>
> Performance boost ti
Marek Kierdelewicz wrote:
Hi
Hi
I have a router with a large number of iptables rules and some
extensive traffic shaping (HTB + RED + ... ) + conntrack.
Performance boost tips:
- Use "set" module instead of sequential iptables rules. It can lower
cpu usage.
Hmm - I don't
>Hi
Hi
>I have a router with a large number of iptables rules and some
>extensive traffic shaping (HTB + RED + ... ) + conntrack.
Performance boost tips:
- Use "set" module instead of sequential iptables rules. It can lower
cpu usage.
- Use hashing filters for shaping if you're using many u32
Hi
I have a router with a large number of iptables rules and some extensive
traffic shaping (HTB + RED + ... ) + conntrack.
The router is running Centos5 on a P4 Celeron 2.4 with 512Mb ram
30% soft interrupt cpu utilisation
7000 packets/second on each of eth1 and eth0 (forwarded packets)
20M