From: alekcejk@googlemail.com
To: Eric Dumazet <eric.dumazet@gmail.com>, netdev@vger.kernel.org
Subject: Re: Re: limited network bandwidth with 3.2.x kernels
Date: Mon, 13 Feb 2012 23:16:55 +0200 [thread overview]
Message-ID: <3724891.xPvvFc3DxN@localhost.localdomain> (raw)
In-Reply-To: <1329164293.2523.0.camel@edumazet-laptop>
В сообщении от Понедельник 13 февраля 2012 21:18:13 вы написали:
> Le lundi 13 février 2012 à 22:04 +0200, alekcejk@googlemail.com a
>
> écrit :
> > Hi,
> >
> > I noticed that with 3.2.x kernels download speed from some internet resources
> > became about half of speed that was with previous kernels (3.1 and older).
> > I tested Fedora 15 kernels 2.6.41.10 = 3.1.10 and 2.6.42.3 = 3.2.3
> > (many times rebooted for testing with first and second kernels).
> > See bug https://bugzilla.redhat.com/show_bug.cgi?id=789659
> >
> > lsmod:
> > Module Size Used by
> > nvidia 10778232 40
> > i2c_core 28123 1 nvidia
> > 8139too 32490 0
> > mii 13311 1 8139too
> >
> > dmesg:
> > 8139too: 8139too Fast Ethernet driver 0.9.28
> > 8139too 0000:01:02.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> > 8139too 0000:01:02.0: eth0: RealTek RTL8139 at , IRQ 22
> > 8139too 0000:01:02.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
> >
> > For testing I selected fastest for me download mirrors of FreeBSD and Ubuntu,
> > also I tested download speed from site speedtest.tele2.net.
> >
> > For these sites download speed with 3.1 kernels (and older) is about 11 MB/s
> > but with 3.2.x kernels - limited 5.5 MB/s and for some sites still approximately
> > the same as with 3.1 kernels (see bug mentioned above).
>
> MB/s means MBytes or Mbits ?
MB means MegaBytes. This should explain it:
FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz size 2066424512 bytes (1.9 G) downloaded with both kernels:
kernel 3.1.10: saved in 3m 31s 9,32 Megabytes/second - average speed, 11,1 Megabytes/second maximum
kernel 3.2.3: saved in 5m 56s 5,54 Megabytes/second - average speed, 5,64 Megabytes/s - maximum speed
>
> > Also I want to pay attention that limited speed stays constant - always
> > 5.5 MB/s with straight line on traffic plotter as if was network bandwidth shaping.
> > With 3.1 kernels this never happens - speed can vary in some ranges
> > but at maximum it is about 11 MB/s, no limitations such as 5.5 MB/s.
>
> Could you post "netstat -s" result ?
"netstat -s" just after system started and download finished
kernel 3.1.10:
Ip:
1472431 total packets received
0 forwarded
0 incoming packets discarded
1469765 incoming packets delivered
755430 requests sent out
1 outgoing packets dropped
Icmp:
0 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
1 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
echo request: 1
IcmpMsg:
OutType8: 1
Tcp:
4 active connections openings
0 passive connection openings
0 failed connection attempts
0 connection resets received
0 connections established
1469723 segments received
755378 segments send out
0 segments retransmited
0 bad segments received.
32997 resets sent
Udp:
35 packets received
0 packets to unknown port received.
0 packet receive errors
52 packets sent
0 receive buffer errors
0 send buffer errors
UdpLite:
TcpExt:
1 TCP sockets finished time wait in fast timer
22 delayed acks sent
1448 packets directly received from backlog
1429173 packets header predicted
1 packets header predicted and directly queued to user
2 acknowledgments not containing data received
18 predicted acknowledgments
0 TCP data loss events
1 connections reset due to unexpected data
IPReversePathFilter: 47
IpExt:
InNoRoutes: 218
InMcastPkts: 2
InBcastPkts: 46
OutBcastPkts: 17
InOctets: 2157119711
OutOctets: 38981662
InMcastOctets: 56
InBcastOctets: 3704
OutBcastOctets: 768
kernel 3.2.3:
Ip:
1487136 total packets received
0 forwarded
0 incoming packets discarded
1482687 incoming packets delivered
769964 requests sent out
1 outgoing packets dropped
Icmp:
0 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
1 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
echo request: 1
IcmpMsg:
OutType8: 1
Tcp:
2 active connections openings
0 passive connection openings
0 failed connection attempts
0 connection resets received
0 connections established
1482636 segments received
769905 segments send out
0 segments retransmited
0 bad segments received.
55530 resets sent
Udp:
42 packets received
0 packets to unknown port received.
0 packet receive errors
59 packets sent
0 receive buffer errors
0 send buffer errors
UdpLite:
TcpExt:
1 TCP sockets finished time wait in fast timer
15 delayed acks sent
1425598 packets header predicted
1 acknowledgments not containing data received
9 predicted acknowledgments
0 TCP data loss events
IPReversePathFilter: 48
IpExt:
InNoRoutes: 235
InMcastPkts: 4
InBcastPkts: 47
OutBcastPkts: 17
InOctets: 2143692697
OutOctets: 39392421
InMcastOctets: 112
InBcastOctets: 3941
OutBcastOctets: 768
next prev parent reply other threads:[~2012-02-13 21:17 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 20:04 limited network bandwidth with 3.2.x kernels alekcejk
2012-02-13 20:18 ` Eric Dumazet
2012-02-13 21:13 ` Eric Dumazet
2012-02-13 21:58 ` alekcejk
2012-02-13 22:44 ` Eric Dumazet
2012-02-13 22:51 ` Neal Cardwell
2012-02-13 23:09 ` alekcejk
2012-02-13 23:14 ` Eric Dumazet
2012-02-13 23:24 ` alekcejk
2012-02-13 23:49 ` alekcejk
2012-02-14 3:06 ` Neal Cardwell
2012-02-14 3:26 ` alekcejk
2012-02-14 5:55 ` Eric Dumazet
2012-02-14 14:09 ` alekcejk
2012-02-13 21:16 ` alekcejk [this message]
2012-02-21 4:21 ` alekcejk
2012-02-21 16:45 ` Eric Dumazet
2012-02-21 17:19 ` alekcejk
2012-02-21 17:31 ` Eric Dumazet
2012-02-21 18:53 ` alekcejk
2012-02-22 1:26 ` alekcejk
[not found] ` <1920135.kl3o7Tt79c@localhost.localdomain>
[not found] ` <1329228798.4818.0.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
2012-02-14 14:28 ` alekcejk
2012-02-14 16:00 ` Eric Dumazet
2012-02-14 16:43 ` alekcejk
2012-02-15 4:43 ` Eric Dumazet
2012-02-15 6:03 ` Neal Cardwell
2012-02-15 6:06 ` Eric Dumazet
2012-02-15 7:52 ` Bill Fink
2012-02-15 8:00 ` Eric Dumazet
2012-02-15 8:18 ` Bill Fink
2012-02-15 8:31 ` Eric Dumazet
2012-02-15 13:44 ` alekcejk
2012-02-15 13:43 ` Re: Re: Re: Re: " alekcejk
2012-02-15 13:44 ` alekcejk
2012-02-15 13:49 ` Eric Dumazet
2012-02-15 13:53 ` Eric Dumazet
2012-02-15 14:11 ` alekcejk
2012-02-15 14:49 ` Neal Cardwell
2012-02-15 14:56 ` Eric Dumazet
2012-02-15 15:05 ` alekcejk
2012-02-15 15:08 ` Eric Dumazet
2012-02-15 19:44 ` Neal Cardwell
2012-02-16 7:29 ` Eric Dumazet
2012-02-16 13:40 ` Eric Dumazet
2012-02-16 13:51 ` Ben Hutchings
2012-02-16 15:09 ` Eric Dumazet
2012-02-16 16:37 ` Ben Hutchings
2012-02-16 17:01 ` David Miller
2012-02-16 17:22 ` Neal Cardwell
2012-02-16 17:54 ` alekcejk
2012-02-16 18:19 ` Neal Cardwell
2012-02-16 21:49 ` alekcejk
2012-02-16 21:59 ` Eric Dumazet
2012-02-16 22:08 ` alekcejk
2012-02-16 22:35 ` Eric Dumazet
2012-02-17 16:41 ` Neal Cardwell
2012-02-21 18:41 ` Eric Dumazet
2012-02-21 19:11 ` David Miller
2012-02-22 5:51 ` Neal Cardwell
2012-02-22 7:36 ` Eric Dumazet
2012-02-23 18:39 ` Neal Cardwell
2012-02-23 18:49 ` Eric Dumazet
2012-02-27 19:39 ` David Miller
2012-02-17 16:55 ` Re: " Neal Cardwell
2012-02-16 18:22 ` Eric Dumazet
2012-02-16 19:44 ` Eric Dumazet
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=3724891.xPvvFc3DxN@localhost.localdomain \
--to=alekcejk@googlemail.com \
--cc=eric.dumazet@gmail.com \
--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).