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 17:09:06 +0200 [thread overview]
Message-ID: <4AA7C512.6040100@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0909091000200.28070@V090114053VZO-1>
Christoph Lameter a écrit :
> On Wed, 9 Sep 2009, Eric Dumazet wrote:
>
>> 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
>
> I use the above setup.
Then frames are sent on wire but not received
(they are received via mc loop, internal stack magic)
# ./mcast -L -n1 -r 10000
WARNING: Multiple active ethernet devices. Using local address 192.168.0.1
Receiver: Listening to control channel 239.0.192.1
Receiver: Subscribing to 1 MC addresses 239.0.192-254.2-254 offset 0 origin 192.168.0.1
Sender: Sending 10000 msgs/ch/sec on 1 channels. Probe interval=0.001-1 sec.
TotalMsg Lost SeqErr TXDrop Msg/Sec KB/Sec Min/us Avg/us Max/us StdDv
100000 0 0 0 10000 3000.0 7.84 8.89 10.51 0.66
# uname -a
Linux erd 2.6.30.5 #2 SMP Mon Sep 7 17:15:43 CEST 2009 i686 i686 i386 GNU/Linux
I tried an old kernel on same hardware :
# ./mcast -L -n1 -r 10000
WARNING: Multiple active ethernet devices. Using local address 55.225.18.6
Receiver: Listening to control channel 239.0.192.1
Receiver: Subscribing to 1 MC addresses 239.0.192-254.2-254 offset 0 origin 55.225.18.6
Sender: Sending 10000 msgs/ch/sec on 1 channels. Probe interval=0.001-1 sec.
TotalMsg Lost SeqErr TXDrop Msg/Sec KB/Sec Min/us Avg/us Max/us StdDv
99999 0 0 0 9998 0.0 9.00 9.95 14.50 1.56
Linux erd 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux
So my numbers seem much better than yours...
next prev parent reply other threads:[~2009-09-09 15:09 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
2009-09-09 14:01 ` Christoph Lameter
2009-09-09 15:09 ` Eric Dumazet [this message]
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=4AA7C512.6040100@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 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.