From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dan" Date: Wed, 24 Jan 2007 17:22:14 +0000 Subject: [LARTC] Thoughput Message-Id: <006f01c73fdc$30f4c0d0$92de4270$@eu> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0558200135==" List-Id: To: lartc@vger.kernel.org This is a multipart message in MIME format. --===============0558200135== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0070_01C73FDC.30F4C0D0" Content-Language: en-gb This is a multipart message in MIME format. ------=_NextPart_000_0070_01C73FDC.30F4C0D0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I am after a feel of the throughput capabilities for TC and Iptables in comparison to dedicated hardware. I have heard talk about 1Gb+ throughput with minimal performance impact using 50ish TC rules and 100+ Iptables rules. Is there anyone here running large throughput / large configurations, and if so, what sort of figures? Regards Dan ------=_NextPart_000_0070_01C73FDC.30F4C0D0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

I am after a feel of the throughput capabilities = for TC and Iptables in comparison to dedicated hardware. I have heard talk about = 1Gb+ throughput with minimal performance impact using 50ish TC rules and 100+ Iptables = rules.

Is there anyone here running large throughput / = large configurations, and if so, what sort of figures?

Regards

Dan

------=_NextPart_000_0070_01C73FDC.30F4C0D0-- --===============0558200135== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============0558200135==--