public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jesper Dangaard Brouer <jdb@comx.dk>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Loopback performance from kernel 2.6.12 to 2.6.37
Date: Tue, 09 Nov 2010 15:06:12 +0100	[thread overview]
Message-ID: <1289311573.18992.1.camel@edumazet-laptop> (raw)
In-Reply-To: <1289311159.17448.9.camel@traveldev.cxnet.dk>

Le mardi 09 novembre 2010 à 14:59 +0100, Jesper Dangaard Brouer a
écrit :
> On Mon, 2010-11-08 at 16:06 +0100, Eric Dumazet wrote:
> ...
> > > > > > I noticed that the loopback performance has gotten quite bad:
> > > > > > 
> > > > > > http://www.phoronix.com/scan.php?page=article&item=linux_2612_2637&num=6
> > >
> 
> > CC netdev, if you dont mind.
> 
> No problem :-)
> 
> > Their network test is basically :
> > 
> > netcat -l 9999 >/dev/null &
> > time dd if=/dev/zero bs=1M count=10000 | netcat  127.0.0.1 9999
> 
> Should it not be:
>  netcat -l -p 9999 >/dev/null &
> 

It depends on netcat version. On yours, yes, you need the "-p"

> When I run the commands "dd | netcat", netcat never finish/exits, I have
> to press Ctrl-C to stop it.  What am I doing wrong? Any tricks?
> 
> "dd" reports 17.54 sec, and but the "time" measurement cannot be uses as
> the netcat just hangs/waits for more data...
> 

Your netcat version needs a "-c" switch

time dd if=/dev/zero bs=1M count=10000 | netcat -c 127.0.0.1 9999


> time dd if=/dev/zero bs=1M count=10000 | netcat 127.0.0.1 9999
> 10000+0 records in
> 10000+0 records out
> 10485760000 bytes (10 GB) copied, 17,5419 s, 598 MB/s
> 
> When I run the commands, I see 261682 context switches per sec...
> 
> This quick test were on a Core i7 920 using kernel
> 2.6.32-rc3-net-next-dev-mp2t.
> 

32 or 64bit kernel ?

Thanks !




  reply	other threads:[~2010-11-09 14:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1288954189.28003.178.camel@firesoul.comx.local>
     [not found] ` <1288988955.2665.297.camel@edumazet-laptop>
     [not found]   ` <1289213926.15004.19.camel@firesoul.comx.local>
     [not found]     ` <1289214289.2820.188.camel@edumazet-laptop>
2010-11-08 15:06       ` Loopback performance from kernel 2.6.12 to 2.6.37 Eric Dumazet
2010-11-09  0:05         ` Andrew Hendry
2010-11-09  5:22           ` Eric Dumazet
2010-11-09  6:23             ` Eric Dumazet
2010-11-09  6:30               ` Andrew Hendry
2010-11-09  6:38                 ` Eric Dumazet
2010-11-09  6:42                   ` Eric Dumazet
2010-11-09 13:59         ` Jesper Dangaard Brouer
2010-11-09 14:06           ` Eric Dumazet [this message]
2010-11-09 14:16           ` Jesper Dangaard Brouer
2010-11-09 14:25             ` Eric Dumazet
2010-11-18 13:52               ` Eric Dumazet
2010-11-18 17:41                 ` Eric Dumazet
2010-11-18 17:48                   ` David Miller
2010-11-09 14:38             ` Jesper Dangaard Brouer
2010-11-10 11:24               ` Jesper Dangaard Brouer
2010-12-12 15:48                 ` Arnaldo Carvalho de Melo
2010-11-09 21:35 Xose Vazquez Perez
2010-11-10  8:49 ` Jesper Dangaard Brouer

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=1289311573.18992.1.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=jdb@comx.dk \
    --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