linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Bellion and Thomas Heinz <nf@hipac.org>
To: P@draigbrady.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [ANNOUNCE] nf-hipac v0.8 released
Date: Wed, 2 Jul 2003 15:48:19 +0200	[thread overview]
Message-ID: <200307021548.19989.nf@hipac.org> (raw)
In-Reply-To: <3F02D964.7050301@draigBrady.com>

Hi Pádraig

> > Since real world network traffic always consists of a lot of different
> > sized packets taking maximum sized packets is very euphemistic. 1450 byte
> > packets at 950 Mbit/s correspond to approx. 80,000 packets/sec.
> > We are really interested in how our algorithm performs at higher packet
> > rates. Our performance tests are based on 100 Mbit hardware so we coudn't
> > test with more than approx. 80,000 packets/sec even with minimum sized
> > packets.
>
> Interrupt latency is the problem here. You'll require napi et. al
> to get over this hump.

Yes we know, but with 128 byte frame size you can archieve a packet rate of at 
most 97,656 packets/sec (in theory) on 100 Mbit hardware. We don't think this 
few more packets would have changed the results fundamentally, so it's 
probably not worth it on 100 Mbit.
Certainly you are right, that napi is required on gigabit to saturate the link 
with small sized packets. 

> Cool. The same sort of test with ordinary netfilter that
> I did showed it could only handle around 125 rules at this
> packet rate on a 1.4GHz PIII, e1000 @ 100Mb/s.
>
> # ./readprofile -m /boot/System.map | sort -nr | head -30
>    6779 total                                      0.0047
>    4441 default_idle                              69.3906
>     787 handle_IRQ_event                           7.0268
>     589 ip_packet_match                            1.6733
>     433 ipt_do_table                               0.6294
>     106 eth_type_trans                             0.5521
>     [...]

What do you want to show with this profile? Most of the time is spend in the 
idle loop and in icq handling and only a few percentage in ip_packet_match 
and ipt_do_table, so we don't quite get how this matches your statement 
above. Could you explain this in a few words?

Regards,

+-----------------------+----------------------+
|   Michael Bellion     |     Thomas Heinz     |
| <mbellion@hipac.org>  |  <creatix@hipac.org> |
+-----------------------+----------------------+


  reply	other threads:[~2003-07-02 13:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 20:48 [ANNOUNCE] nf-hipac v0.8 released Michael Bellion and Thomas Heinz
2003-06-25 21:03 ` Folkert van Heusden
2003-06-25 23:52   ` Thomas Heinz
2003-06-26 13:38 ` Daniel Egger
2003-06-26 14:20   ` Michael Bellion and Thomas Heinz
2003-06-26 14:45     ` Daniel Egger
2003-06-27  6:06 ` Pekka Savola
2003-06-28 20:04   ` Michael Bellion and Thomas Heinz
2003-06-29  6:26     ` Pekka Savola
2003-06-29  7:45       ` Roberto Nibali
2003-06-29 16:26       ` Michael Bellion and Thomas Heinz
2003-07-02  5:30         ` Pekka Savola
2003-07-02 12:26           ` Michael Bellion and Thomas Heinz
2003-07-02 13:08             ` P
2003-07-02 13:48               ` Michael Bellion and Thomas Heinz [this message]
2003-07-02 14:23                 ` P
2003-07-02 16:57                   ` Michael Bellion and Thomas Heinz

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=200307021548.19989.nf@hipac.org \
    --to=nf@hipac.org \
    --cc=P@draigbrady.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).