From: Eric Dumazet <eric.dumazet@gmail.com>
To: adam.niescierowicz@justnet.pl
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: 3.4.1 and 3.5-rc1 Packet lost at 250Mb/s
Date: Fri, 06 Jul 2012 12:13:29 +0200 [thread overview]
Message-ID: <1341569609.3265.389.camel@edumazet-glaptop> (raw)
In-Reply-To: <2d2806e8e8ecad5646524acf2c4c5bcf@justnet.pl>
On Fri, 2012-07-06 at 11:47 +0200, Nieścierowicz Adam wrote:
> Hello,
> Can I send something that will help determine the cause of the problem?
>
>
> W dniu 08.06.2012 11:41, Eric Dumazet napisał(a):
>
> > On Fri, 2012-06-08 at 10:58 +0200, Nieścierowicz Adam wrote:
> >
> >> Hello, recently we changed on the router kernel from 2.6.38.1 to
> >> 3.4.1
> >> and noticed 30% packet loss when traffic increases up to 250MB / s.
> >> Similar is for kernel 3.5-rc1 Here a link to ifstat
> >> http://wklej.org/id/767577/ [2]
> >
> > You should give as much as possible delails on your setup (hardware,
> > software)
> >
> > lspci
> > cat /proc/cpuinfo
> > cat /proc/interrupts
> > ifconfig -a
> > tc -s -d qdisc
> > dmesg
> > netstat -s
>
> currently running on 2.6.38.1 and traffic is 100Mb / s
>
> lspci: http://wklej.org/id/769102/
> /proc/cpuinfo: http://wklej.org/id/769104/
> /proc/interrupts: http://wklej.org/id/769106/
> ifconfig -a: http://wklej.org/id/769108/
> tc -s -d qdisc: http://wklej.org/id/769109/
> dmesg: here are some logs from iptables
> netstat -s: http://wklej.org/id/769110/
> lsmod: http://wklej.org/id/769117/
> /proc/net/softnet_stat: http://wklej.org/id/769116/
Same infos of 3.5-rcX kernel would be nice.
What NIC is eth0 ? (dmesg please)
It seems all network traffic on 2.6.38 is handled by a single cpu (cpu0)
(seen in /proc/interrupts)
I suspect that with 3.4 or 3.5 kernels, traffic is handled by many cpus
and they hit false sharing and contention.
You probably get better performance doing some affinity tuning :
For example,
eth0 serviced by cpu0
eth2 serviced by cpu1
eth3 serviced by cpu2
eth5 serviced by cpu3
and so on...
check and/or set /proc/irq/${NUM}/smp_affinity
next prev parent reply other threads:[~2012-07-06 10:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 9:47 3.4.1 and 3.5-rc1 Packet lost at 250Mb/s Nieścierowicz Adam
2012-07-06 10:13 ` Eric Dumazet [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-07 19:18 Nieścierowicz Adam
2012-10-08 6:22 ` Eric Dumazet
2012-10-08 9:29 ` Nieścierowicz Adam
2012-10-08 9:47 ` Eric Dumazet
2012-10-08 10:49 ` Nieścierowicz Adam
2012-10-08 12:00 ` Andre Tomt
2012-10-08 12:06 ` Nieścierowicz Adam
2012-10-08 12:13 ` Eric Dumazet
2012-10-08 12:32 ` Andre Tomt
2012-10-08 12:59 ` Andre Tomt
2012-10-09 19:56 ` Nieścierowicz Adam
2012-10-10 4:59 ` Jeff Kirsher
2012-06-08 9:31 Nieścierowicz Adam
2012-06-08 8:58 Nieścierowicz Adam
2012-06-08 9:41 ` Eric Dumazet
2012-06-08 9:43 ` 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=1341569609.3265.389.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=adam.niescierowicz@justnet.pl \
--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