From: Stephan von Krawczynski <skraw@ithnet.com>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: willy@w.ods.org, linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: hidden interface (ARP) 2.4.20 / network performance
Date: Tue, 10 Dec 2002 14:09:12 +0100 [thread overview]
Message-ID: <20021210140912.7a9092b6.skraw@ithnet.com> (raw)
In-Reply-To: <3DF5C492.1070103@drugphish.ch>
On Tue, 10 Dec 2002 11:40:18 +0100
Roberto Nibali <ratz@drugphish.ch> wrote:
> > This is unfortunately not sufficient, not even close to. If you really want
> > to have a good idea what is going on you should as well check out what is
> > happening with packet sizes a lot smaller than 1500 (normal mtu). Check
> > data rate an packet loss with packet sizes around 80 bytes or so to get an
> > idea what bothers us :-)
>
> But this doesn't have anything to do with the hidden patch! It can be
> multiple things:
>
> o missing TCP segment offload support
> o inefficient zerocopy DMA support
cannot comment these.
> o IRQ routing problems
no.
> o wrong QoS settings
no.
> Could you please be more specific on what exactly you're trying to
> achieve? Do you want to load balance an application whose average
> package size is 80 bytes? How many sustained connections per seconds do
> you have?
Well, what I am trying to say is this: my experience is that under load with
small sized packets even standard routing/packet forwarding becomes lossy. If I
put NAT and other nice netfilter features on top of such a situation things get
a lot worse (obviously) - no comparison to building the "application" (e.g.
cluster) with routing and hidden-patch (mainly because of its pure simplicity I
guess).
Don't get me wrong: I am pretty content with the hidden-patch and my setup
without NAT. But I wanted to point to the direction of possible further routing
performance improvement in 2.4.X tree. Is it correct that I can expect higher
data-rates (concerning small packets) if using higher HZ ?
Someone selling E3 cards told me he cannot manage loads like these (small
packet stuff) with a stock kernel, and that you _at least_ have to increase HZ
to get acceptable throughput results.
--
Regards,
Stephan
next prev parent reply other threads:[~2002-12-10 13:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 20:53 hidden interface (ARP) 2.4.20 Bingner Sam J Contractor PACAF CSS/SCHE
2002-12-05 21:42 ` David S. Miller
2002-12-05 22:03 ` Phil Oester
2002-12-05 22:50 ` Roberto Nibali
2002-12-05 23:48 ` Phil Oester
2002-12-05 23:59 ` Roberto Nibali
2002-12-06 6:01 ` Willy Tarreau
2002-12-06 17:52 ` Stephan von Krawczynski
2002-12-07 23:30 ` Roberto Nibali
2002-12-08 16:03 ` Stephan von Krawczynski
2002-12-08 17:01 ` Willy Tarreau
2002-12-09 11:08 ` Stephan von Krawczynski
2002-12-10 9:42 ` Gilad Ben-Yossef
2002-12-10 10:40 ` Roberto Nibali
2002-12-10 13:09 ` Stephan von Krawczynski [this message]
2002-12-10 18:11 ` hidden interface (ARP) 2.4.20 / network performance Roberto Nibali
2002-12-10 23:29 ` Willy TARREAU
2002-12-10 1:22 ` hidden interface (ARP) 2.4.20 Bill Davidsen
2002-12-10 10:40 ` Roberto Nibali
2002-12-10 14:47 ` Bill Davidsen
2002-12-10 18:15 ` Roberto Nibali
2002-12-11 16:15 ` Bill Davidsen
2002-12-12 1:33 ` Bernd Eckenfels
2002-12-05 22:18 ` Martin Josefsson
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=20021210140912.7a9092b6.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=ratz@drugphish.ch \
--cc=willy@w.ods.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox