[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dpdk-users
Subject:    [dpdk-users] DPDK 17.11.4 failover with Intel X722 card
From:       Greg O'Rawe <greg.orawe () enea ! com>
Date:       2019-07-04 16:23:21
Message-ID: AM6PR03MB484055DEBA05666DB53E3F81EDFA0 () AM6PR03MB4840 ! eurprd03 ! prod ! outlook ! com
[Download RAW message or body]

Hi,


I have an X722 adapter using the i40e driver deployed with DPDK 17.11.4 on =
Red Hat 7.5 Linux system.



System is set up to bond two interfaces and then two VLANs on the bond for =
client and server traffic.



This works with DPDK 17.11.4 except that failover of interfaces within the =
bond does not work correctly. Change of status on an interface is not detec=
ted.



Driver version is 2.9.21 and firmware 4.00 0x8000183f 1.1937.0


# ethtool -i eno2

driver: i40e

version: 2.9.21

firmware-version: 4.00 0x8000183f 1.1937.0

expansion-rom-version:

bus-info: 0000:09:00.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes



# lspci | grep -i ether

09:00.0 Ethernet controller: Intel Corporation Ethernet Connection X722 for=
 10GbE backplane (rev 09)

09:00.1 Ethernet controller: Intel Corporation Ethernet Connection X722 for=
 10GbE backplane (rev 09)

09:00.2 Ethernet controller: Intel Corporation Ethernet Connection X722 for=
 10GbE backplane (rev 09)

09:00.3 Ethernet controller: Intel Corporation Ethernet Connection X722 for=
 10GbE backplane (rev 09)

Is there any reason why failover would not work in this case within DPDK?

Thanks
Greg O'Rawe

This message, including attachments, is CONFIDENTIAL. It may also be privil=
eged or otherwise protected by law. If you received this email by mistake p=
lease let us know by reply and then delete it from your system; you should =
not copy it or disclose its contents to anyone. All messages sent to and fr=
om Enea may be monitored to ensure compliance with internal policies and to=
 protect our business. Emails are not secure and cannot be guaranteed to be=
 error free as they can be intercepted, a mended, lost or destroyed, or con=
tain viruses. The sender therefore does not accept liability for any errors=
 or omissions in the contents of this message, which arise as a result of e=
mail transmission. Anyone who communicates with us by email accepts these r=
isks.
[prev in list] [next in list] [prev in thread] [next in thread]