Hi Todd,
Thank you for your information. We'll contract our support.

Best Regards,
Liu Wei

-----Original Message-----
From: Fujinaka, Todd [mailto:todd.fujin...@intel.com] 
Sent: 2014年9月29日 23:23
To: Wei Liu; e1000-de...@lists.sf.net
Cc: 'Haifeng Li'; dxzh...@fortinet.com; yut...@fortinet.com
Subject: RE: [E1000-devel] i40e nics are down when I use them on Dual CPU

I think you need to update the NICs. Please contact your factory support. We
won't be able to provide that level of support on this mailing list.

Thanks.

Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565

-----Original Message-----
From: Wei Liu [mailto:liu...@fortinet.com] 
Sent: Sunday, September 28, 2014 7:58 PM
To: e1000-de...@lists.sf.net
Cc: 'Haifeng Li'; dxzh...@fortinet.com; yut...@fortinet.com
Subject: [E1000-devel] i40e nics are down when I use them on Dual CPU

Hi All,

 

When we use netperf to generate traffic, i40e nics are down very soon( the
throughput is about 76Gbps).

 

CPU: "Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz" X2

 

TOPO: 

port5, port6, port11, port12 are i40e interfaces.

port6 and port12 are in a net namespace.

port5<--->port6: port5 is connected port6 directly.

port11<--->port12: port11 is connected port12 directly.

 

nics interrupt bind cpu:

port5: 0, 1, 2, 3, 4 (CPU0)

port6: 10, 11, 12, 13, 14 (CPU1)

port11: 5, 6, 7, 8, 9(CPU0)

port12: 15, 16, 17, 18, 19 (CPU1)

 

kernel: 3.13.11

driver: i40e stable
1.0.15(http://sourceforge.net/projects/e1000/files/i40e%20stable/1.0.15/):

version: 1.0.15

firmware-version: f4.1 a1.1 n04.10 e800010e0

bus-info: 0000:09:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: no

 

netperf cmd:

netperf -T 14,19 -L 15.3.2.1 -H 15.3.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 13,18 -L 15.5.2.1 -H 15.5.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 12,17 -L 15.2.2.1 -H 15.2.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 11,16 -L 15.1.2.1 -H 15.1.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 10,15 -L 15.4.2.1 -H 15.4.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 4,9 -L 14.4.2.1 -H 14.4.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 3,8 -L 14.1.2.1 -H 14.1.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 2,7 -L 14.5.2.1 -H 14.5.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 1,6 -L 14.2.2.1 -H 14.2.1.100 -f m -D 1 -l 600 >/dev/null &

netperf -T 0,5 -L 14.3.2.1 -H 14.3.1.100 -f m -D 1 -l 600 >/dev/null &

 

dmesg:

...

i40e 0000:09:00.1 port6: NIC Link is Up 40 Gbps Full Duplex, Flow Control:
None

i40e 0000:09:00.0 port5: NIC Link is Up 40 Gbps Full Duplex, Flow Control:
None

IPv6: ADDRCONF(NETDEV_CHANGE): port6: link becomes ready

IPv6: ADDRCONF(NETDEV_CHANGE): port5: link becomes ready

i40e 0000:8a:00.0 port11: NIC Link is Up 40 Gbps Full Duplex, Flow Control:
None

i40e 0000:8a:00.1 port12: NIC Link is Up 40 Gbps Full Duplex, Flow Control:
None

IPv6: ADDRCONF(NETDEV_CHANGE): port11: link becomes ready

IPv6: ADDRCONF(NETDEV_CHANGE): port12: link becomes ready

------------[ cut here ]------------

WARNING: at net/sched/sch_generic.c:254 dev_watchdog+0x174/0x1da()

Hardware name: To be filled by O.E.M.

NETDEV WATCHDOG: port5 (i40e): transmit queue 3 timed out

Modules linked in: i40e(O) ixgbe(O)

Pid: 883, comm: kworker/0:1 Tainted: G           O 3.8.4+ #1

Call Trace:

<IRQ>  [<ffffffff8022d914>] ? warn_slowpath_common+0x76/0x8a

[<ffffffff8022d96f>] ? warn_slowpath_fmt+0x47/0x49

[<ffffffff802373b5>] ? mod_timer+0x107/0x11b

[<ffffffff80549ec7>] ? dev_watchdog+0x174/0x1da

[<ffffffff80549d53>] ? dev_graft_qdisc+0x61/0x61

[<ffffffff802375e8>] ? call_timer_fn.isra.35+0x1c/0x6f

[<ffffffff8023779e>] ? run_timer_softirq+0x163/0x182

[<ffffffff80232f11>] ? __do_softirq+0xa0/0x13d

[<ffffffff8066260c>] ? call_softirq+0x1c/0x26

[<ffffffff802032b5>] ? do_softirq+0x2a/0x64

[<ffffffff8023306f>] ? irq_exit+0x3d/0x5a

[<ffffffff80218af2>] ? smp_apic_timer_interrupt+0x81/0x8d

[<ffffffff8066200a>] ? apic_timer_interrupt+0x6a/0x70

<EOI>  [<ffffffffa003e220>] ? i40e_do_reset_safe+0xcd2/0xd84 [i40e]

[<ffffffffa003dff5>] ? i40e_do_reset_safe+0xaa7/0xd84 [i40e]

[<ffffffff803af706>] ? delay_tsc+0x20/0x44

[<ffffffffa0042412>] ? i40e_asq_send_command+0x316/0x441 [i40e]

[<ffffffffa0043546>] ? i40e_aq_get_link_info+0x47/0x123 [i40e]

[<ffffffffa0043d64>] ? i40e_get_link_status+0x20/0x28 [i40e]

[<ffffffffa0036e45>] ? i40e_ioctl+0x1858/0x1a0b [i40e]

[<ffffffffa003e228>] ? i40e_do_reset_safe+0xcda/0xd84 [i40e]

[<ffffffff802370ca>] ? internal_add_timer+0xd/0x28

[<ffffffff802373b5>] ? mod_timer+0x107/0x11b

[<ffffffff8023f37e>] ? process_one_work+0x1d6/0x2d8

[<ffffffff8023f6a4>] ? worker_thread+0x201/0x2eb

[<ffffffff8023f4a3>] ? process_scheduled_works+0x23/0x23

[<ffffffff80243034>] ? kthread+0xa9/0xb1

[<ffffffff80242f8b>] ? kthread_stop+0x49/0x49

[<ffffffff8066146c>] ? ret_from_fork+0x7c/0xb0

[<ffffffff80242f8b>] ? kthread_stop+0x49/0x49

---[ end trace bdce93fbb0280b12 ]---

i40e 0000:09:00.0 port5: tx_timeout recovery level 1

i40e 0000:09:00.0: i40e_vsi_control_tx: VSI seid 518 Tx ring 3 disable
timeout

i40e 0000:09:00.0: i40e_ptp_init: added PHC on port5

i40e 0000:09:00.0 port5: adding 00:90:0b:38:4f:7c vid=0

i40e 0000:09:00.0 port5: set fc fail, aq_err -7

i40e 0000:09:00.0 port5: NIC Link is Up 40 Gbps Full Duplex, Flow Control:
None

i40e 0000:09:00.0 port5: NIC Link is Down

i40e 0000:09:00.1 port6: NIC Link is Down

i40e 0000:09:00.1 port6: NIC Link is Up 40 Gbps Full Duplex, Flow Control:
None

i40e 0000:09:00.0 port5: NIC Link is Up 40 Gbps Full Duplex, Flow Control:
None

...

 

Regards,

Liu Wei

 

skype:      lw1a2_jing

ext:        8025

 



***  Please note that this message and any attachments may contain
confidential and proprietary material and information and are intended only
for the use of the intended recipient(s). If you are not the intended
recipient, you are hereby notified that any review, use, disclosure,
dissemination, distribution or copying of this message and any attachments
is strictly prohibited. If you have received this email in error, please
immediately notify the sender and destroy this e-mail and any attachments
and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments
expressed in this message are those of the individual sender and do not
necessarily reflect the views of Fortinet, Inc., its affiliates, and emails
are not binding on Fortinet and only a writing manually signed by Fortinet's
General Counsel can be a binding commitment of Fortinet to Fortinet's
customers or partners. Thank you. ***


***  Please note that this message and any attachments may contain confidential 
and proprietary material and information and are intended only for the use of 
the intended recipient(s). If you are not the intended recipient, you are 
hereby 
notified that any review, use, disclosure, dissemination, distribution or 
copying 
of this message and any attachments is strictly prohibited. If you have 
received 
this email in error, please immediately notify the sender and destroy this 
e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments expressed 
in this message are those of the individual sender and do not necessarily 
reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding on 
Fortinet and only a writing manually signed by Fortinet's General Counsel can 
be 
a binding commitment of Fortinet to Fortinet's customers or partners. Thank 
you. ***


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to