Re: [LARTC] Which CPU for heavy traffic with much filtering/shaping?

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

Re: [LARTC] Which CPU for heavy traffic with much filtering/shaping?

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

Re: [LARTC] Which CPU for heavy traffic with much filtering/shaping?

>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

RE: [LARTC] Unexpected results using HTB qdisc

Hi John, Thanks for the reply. I removed the ceil parameters as a troubleshooting process to ensure that they weren't what was causing the excess of the configured rate. From what I can see if the ceil parameter is not specified it defaults to the same figure as the rate parameter. I have

Re: [LARTC] neighbor table overflow

> Still beating the same bush! > > I've done all the possible suggestions so far. I still was getting > a neighbor table overflow. ... If this can help. Have same problem when testing new server in network (kernel is 2.6.21.5) - everything seems OK in system except neighbor table overflow, and

Re: [LARTC] Which CPU for heavy traffic with much filtering/shaping?

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

Re: [LARTC] neighbor table overflow

Still beating the same bush! I've done all the possible suggestions so far. I still was getting a neighbor table overflow. Looking at the MAN 7 ARP pages, I see: gc_thresh1 The minimum number of entries to keep in the ARP cache. The garbage collector will not run if there

[LARTC] Changing TBF rate on the fly results in drops?

Hi everybody, it is my first message here. I tried to browse throughout older posts but I found no immediate answer. I need to change rate of a tbf queue while ip packets are already enqueued by it. If I go: tc qdisc replace|change|link dev eth0 root tbf rate 180kbit burst 1540 limit 1540

Re: [LARTC] Unexpected results using HTB qdisc

Hi Stuart Clouston wrote: Hi All, I am using the script below to limit download rates and manage traffic for a certain IP address and testing the results using iperf. The rate that iperf reports is much higher than the rate I have configured for the HTB qdisc. It's probably just some newbi

Re: [LARTC] Which CPU for heavy traffic with much filtering/shaping?

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

Re: [LARTC] Which CPU for heavy traffic with much filtering/shaping?

>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

[LARTC] Which CPU for heavy traffic with much filtering/shaping?

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