All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Sims <derek@interdart.co.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] Which CPU for heavy traffic with much filtering/shaping?
Date: Mon, 19 Nov 2007 09:42:11 +0000	[thread overview]
Message-ID: <47415A73.9020107@interdart.co.uk> (raw)

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)
20Mbit/second on both eth1 and eth0
e1000 ethernet on both eth0 and eth1 (eth1 running at 100Mbit)

I am trying to optimise the firewall rules and have already managed to 
reduce cpu si by about 40% however I need to get this router to handle a 
throughput rate of 100Mbit or more.

I have seen hints that using SMP (or multicore) processors will not help 
for soft interrupt. My question is this:

1. What processors should I be looking for in order to achieve the best 
routing throughput on a linux router?

2. Is it true that multicore processors will not help much in this 
situation?

Best regards,
Derek
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-11-19  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  9:42 Derek Sims [this message]
2007-11-19 16:40 ` [LARTC] Which CPU for heavy traffic with much filtering/shaping? Marek Kierdelewicz
2007-11-19 17:55 ` Derek Sims
2007-11-19 23:08 ` sawar
2007-11-20  1:03 ` Marek Kierdelewicz
2007-11-20  3:15 ` Mohan Sundaram
2007-11-20  3:30 ` Mohan Sundaram
2007-11-20 16:03 ` Marco C. Coelho

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=47415A73.9020107@interdart.co.uk \
    --to=derek@interdart.co.uk \
    --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.