netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: UDP regression with packets rates < 10k per sec
Date: Wed, 09 Sep 2009 00:52:41 +0200	[thread overview]
Message-ID: <4AA6E039.4000907@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0909081820030.7733@V090114053VZO-1>

Christoph Lameter a écrit :
> Looks like we have a regression since 2.6.22 due to latency increases in
> the network stack? The following is the result of measuring latencies for
> UDP multicast traffic at packet rates of 10pps 100pps 1kpps 10kpps and
> 100k pps. Two system running "mcast -n1 -r<rate>" (mcast tool from
> http://gentwo.org/ll).
> 
> Measurements in microseconds for one hop using bnx2 on Dell R610 (64 bit
> 2.6.31-rc9) and Dell 1950 (32 bit 2.6.22.19 3.3Ghz). Dell R610 RX usecs
> tuned to 0. 32 bit tuned to 1 (NIC is flaky at 0).
> 
> Kernel			10pps	100pps	1kpps	10kpps	100kpps
> ---------------------------------------------------------------
> 2.6.22 (32bit)		30	29.5	29	30	41
> 2.6.31-rc9(64 bit)	64	63	46	30	40
> 
> The only minor improvement is at a rate of 100kpps. All rates
> lower than 10k regress significantly.
> 
> Could there be something wrong with the bnx2 interrupt routing? They all
> end up on cpu0 here. There are 8 of them in a system with 16 "processors".
> How do those need to be configured? There are some sparse comments in
> Documentation/networking/multiqueue.txt but the text does not say anything
> about the irq routing.
> 
> 

Hi Christoph

In order to reproduce this here, could you tell me if you use 

Producer linux-2.6.22 -> Receiver 2.6.22
Producer linux-2.6.31 -> Receiver 2.6.31

Or a mix of
Producer linux-2.6.31 -> Receiver 2.6.22
Producer linux-2.6.22 -> Receiver 2.6.31-rc9

Not clear what is your exact setup

Thanks

  reply	other threads:[~2009-09-08 22:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 22:38 UDP regression with packets rates < 10k per sec Christoph Lameter
2009-09-08 22:52 ` Eric Dumazet [this message]
2009-09-09 14:01   ` Christoph Lameter
2009-09-09 15:09     ` Eric Dumazet
2009-09-09 16:47       ` Christoph Lameter
2009-09-09 17:06         ` Eric Dumazet
2009-09-09 17:55           ` Christoph Lameter
2009-09-10 20:37             ` Eric Dumazet
2009-09-10 21:36               ` Christoph Lameter
2009-09-10 21:37               ` Eric Dumazet
2009-09-10 21:42                 ` Christoph Lameter
2009-09-14 21:10                   ` Christoph Lameter
2009-09-15  5:29                     ` Eric Dumazet
2009-09-15 14:07                       ` Christoph Lameter
2009-09-15 17:26                         ` Eric Dumazet
2009-09-15 20:25                           ` Christoph Lameter
2009-09-15 19:02                             ` Eric Dumazet
2009-09-25 14:19                             ` Eric Dumazet
2009-09-26 16:13                               ` Christoph Lameter
2009-09-10 21:39               ` Christoph Lameter
2009-09-09 17:08         ` Eric Dumazet
2009-09-09 17:26           ` Christoph Lameter

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=4AA6E039.4000907@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=netdev@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 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).