From: Eric Dumazet <eric.dumazet@gmail.com>
To: Wei Gu <wei.gu@ericsson.com>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
netdev <netdev@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: RE: Low performance Intel 10GE NIC (3.2.10) on 2.6.38 Kernel
Date: Mon, 11 Apr 2011 17:42:57 +0200 [thread overview]
Message-ID: <1302536577.4605.1.camel@edumazet-laptop> (raw)
In-Reply-To: <D12839161ADD3A4B8DA63D1A134D084026E4909714@ESGSCCMS0001.eapac.ericsson.se>
Le lundi 11 avril 2011 à 23:14 +0800, Wei Gu a écrit :
> I tried the ixgbe-3.3.8 (insmod ixgbe.ko RSS=8,8,8,8,8,8,8,8 FdirMode=0,0,0,0,0,0,0,0 Node=0,0,1,1,2,2,3,3) from e1000.sf.net both on 2.6.35.1 and 2.6.35.2, same observation as 3.2.10 ixgbe driver, On 2.6.35.2 it have high rx errors:
> Ethtool -S eth10 |grep error
> rx_errors: 0
> tx_errors: 0
> rx_over_errors: 0
> rx_crc_errors: 0
> rx_frame_errors: 0
> rx_fifo_errors: 0
> rx_missed_errors: 2263088
> tx_aborted_errors: 0
> tx_carrier_errors: 0
> tx_fifo_errors: 0
> tx_heartbeat_errors: 0
> rx_long_length_errors: 0
> rx_short_length_errors: 0
> rx_csum_offload_errors: 0
> fcoe_last_errors: 0
>
It would be nice you post perf record / perf report results
During your stress , do
perf record -a -g sleep 10
perf report
And post "top offenders"
Thanks
next prev parent reply other threads:[~2011-04-11 15:43 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D12839161ADD3A4B8DA63D1A134D084026E48B9BEB@ESGSCCMS0001.eapac.ericsson.se>
2011-04-07 4:58 ` Question on "net: allocate skbs on local node" Eric Dumazet
2011-04-07 5:16 ` Eric Dumazet
2011-04-07 6:16 ` Eric Dumazet
2011-04-07 7:22 ` Low performance Intel 10GE NIC (3.2.10) on 2.6.38 Kernel Wei Gu
2011-04-07 8:07 ` Eric Dumazet
2011-04-07 8:39 ` Wei Gu
2011-04-07 9:06 ` Eric Dumazet
2011-04-07 11:15 ` Wei Gu
2011-04-07 11:46 ` Eric Dumazet
2011-04-07 13:41 ` Eric Dumazet
2011-04-07 15:58 ` Alexander Duyck
2011-04-07 16:03 ` Eric Dumazet
2011-04-07 16:20 ` Alexander Duyck
2011-04-07 16:37 ` Eric Dumazet
2011-04-08 8:59 ` Wei Gu
2011-04-08 9:07 ` Eric Dumazet
2011-04-08 9:15 ` Wei Gu
2011-04-08 9:49 ` Eric Dumazet
2011-04-08 9:59 ` Wei Gu
2011-04-08 9:41 ` Wei Gu
2011-04-08 12:19 ` Wei Gu
2011-04-08 12:56 ` Eric Dumazet
2011-04-08 14:10 ` Wei Gu
2011-04-08 14:49 ` Stephen Hemminger
2011-04-09 3:51 ` Wei Gu
2011-04-08 15:07 ` Eric Dumazet
2011-04-09 3:27 ` Wei Gu
2011-04-09 6:36 ` Eric Dumazet
2011-04-10 7:02 ` Wei Gu
2011-04-11 14:50 ` Alexander Duyck
2011-04-11 15:00 ` Wei Gu
2011-04-11 15:14 ` Wei Gu
2011-04-11 15:42 ` Eric Dumazet [this message]
2011-04-12 1:22 ` Wei Gu
2011-04-12 4:40 ` Wei Gu
2011-04-12 4:56 ` Eric Dumazet
2011-04-12 5:18 ` Wei Gu
2011-04-14 5:42 ` Wei Gu
2011-04-14 6:07 ` Eric Dumazet
2011-04-14 6:33 ` Eric Dumazet
2011-04-14 6:58 ` Wei Gu
2011-04-14 16:42 ` Alexander Duyck
2011-04-14 16:45 ` Eric Dumazet
2011-04-14 16:56 ` Peter Zijlstra
2011-04-14 16:57 ` Eric Dumazet
2011-04-14 17:49 ` Eric Dumazet
2011-04-14 19:08 ` Alexander Duyck
2011-04-15 2:10 ` Wei Gu
2011-04-15 8:57 ` Peter Zijlstra
2011-04-15 9:14 ` Wei Gu
2011-04-18 21:12 ` Jesse Brandeburg
2011-04-19 4:09 ` Wei Gu
2011-04-21 2:57 ` Wei Gu
2011-04-21 3:25 ` Wei Gu
2011-04-08 16:22 ` Alexander Duyck
2011-04-09 3:36 ` Wei Gu
2011-04-09 4:40 ` Alexander H Duyck
2011-04-09 6:12 ` Wei Gu
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=1302536577.4605.1.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=wei.gu@ericsson.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