From: Jean-Michel Hautbois <jhautbois@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Rick Jones <rick.jones2@hp.com>, netdev@vger.kernel.org
Subject: Re: TCP communication for raw image transmission
Date: Thu, 5 Jan 2012 10:57:38 +0100 [thread overview]
Message-ID: <CAL8zT=hGnnuXf+cETy9fAeu+aACp2pfL3XfBS_jL_mk38fj4yQ@mail.gmail.com> (raw)
In-Reply-To: <1325757343.2415.6.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
2012/1/5 Eric Dumazet <eric.dumazet@gmail.com>:
> Le jeudi 05 janvier 2012 à 10:48 +0100, Jean-Michel Hautbois a écrit :
>
>> It does not seem to work :
>> netperf -H 192.168.0.1 -l 10 -t UDP_STREAM
>> MIGRATED UDP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
>> 192.168.0.1 (192.168.0.1) port 0 AF_INET
>> Socket Message Elapsed Messages
>> Size Size Time Okay Errors Throughput
>> bytes bytes secs # # 10^6bits/sec
>>
>> 106496 65507 10.01 1836 0 0.00
>> 419227124 0.00 536870912 0.00
>>
>
> Thats because netperf -t UDP_STREAM sends big UDP frames by default,
> that must be fragmented, and defragmented on destination. Maybe some
> frags are lost.
>
> Try :
>
> netperf -H 192.168.0.1 -l 10 -t UDP_STREAM -- -m 1500
>
>
/ # netperf -H 192.168.0.1 -c -l 10 -t UDP_STREAM -- -m 1500
MIGRATED UDP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
192.168.0.1 (192.168.0.1) port 0 AF_INET
Socket Message Elapsed Messages CPU Service
Size Size Time Okay Errors Throughput Util Demand
bytes bytes secs # # 10^6bits/sec % SU us/KB
106496 1500 10.00 54477 0 0.0 65.34 100.000
1073741824 2.25 0 0.0 65.34 -1.000
/ # netperf -H 192.168.0.1 -c -l 10 -t UDP_STREAM -- -m 1400
MIGRATED UDP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
192.168.0.1 (192.168.0.1) port 0 AF_INET
Socket Message Elapsed Messages CPU Service
Size Size Time Okay Errors Throughput Util Demand
bytes bytes secs # # 10^6bits/sec % SU us/KB
106496 1400 10.00 73591 0 0.0 82.38 100.000
-2147483648 2.25 1610612736 0.0 82.38 -1.000
I will recompile my kernel in order to use perf as well, in order to
get profiling in the TCP case...
JM
next prev parent reply other threads:[~2012-01-05 9:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 15:21 TCP communication for raw image transmission Jean-Michel Hautbois
2012-01-02 15:59 ` Eric Dumazet
2012-01-02 16:08 ` Jean-Michel Hautbois
2012-01-02 16:29 ` Eric Dumazet
2012-01-02 16:40 ` Jean-Michel Hautbois
2012-01-02 16:52 ` Eric Dumazet
2012-01-02 16:52 ` Eric Dumazet
2012-01-02 17:04 ` Jean-Michel Hautbois
2012-01-02 17:20 ` Jean-Michel Hautbois
2012-01-02 17:41 ` Eric Dumazet
2012-01-02 18:00 ` Jean-Michel Hautbois
2012-01-02 18:02 ` Jean-Michel Hautbois
2012-01-03 7:36 ` Jean-Michel Hautbois
2012-01-03 8:06 ` Eric Dumazet
2012-01-05 8:50 ` Jean-Michel Hautbois
2012-01-03 22:35 ` Rick Jones
2012-01-05 9:13 ` Jean-Michel Hautbois
2012-01-05 9:40 ` Eric Dumazet
2012-01-05 9:48 ` Jean-Michel Hautbois
2012-01-05 9:55 ` Eric Dumazet
2012-01-05 9:57 ` Jean-Michel Hautbois [this message]
2012-01-05 10:04 ` Eric Dumazet
2012-01-05 18:41 ` Rick Jones
2012-01-05 18:53 ` Eric Dumazet
2012-01-05 19:26 ` Rick Jones
2012-01-05 18:32 ` Rick Jones
2012-01-05 9:49 ` Eric Dumazet
2012-01-04 9:57 ` David Laight
2012-01-04 11:16 ` Jean-Michel Hautbois
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='CAL8zT=hGnnuXf+cETy9fAeu+aACp2pfL3XfBS_jL_mk38fj4yQ@mail.gmail.com' \
--to=jhautbois@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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).