[dpdk-test-report] [PatchWork]|SUCCESS| pw11741 ethdev: 100G and link speed>> > > API refactoring>> > >>> > > 2016-03-17 19:08, Thomas Monjalon:>> > > > There are still too few tests and reviews, especially for>> > > > autonegotiation with Intel devices (patch #6).>> > > > I would not be surprised to see some bugs in this rework.>> > >>> > > Any feedback about autoneg in e1000/ixgbe/i40e?>> > > Has it been tested before its integration in RC2?>> > >>> > > > The capabilities must be adapted per device. It can be improved in a>> > > > separate patch.>> > > >>> > > > It will be integrated in 16.04-rc2.>> > > > Please test and review shortly, thanks!>> > >>> > >>> > > ---------- Forwarded message ---------->> > > RE: DPDK link speed with Intel devices Hi, all We have worked>> > > out the basic test cases for the patchset.>> > > 1. Test the link speed on major Intel NICs to see if the speed is>> right.>> > > 2. Test the auto-negoation on major Intel NICs to ensure it's working.>> > > Nic covered: ixgbe, igb, i40e, fm10k, bonding(SW), virtio(SW)>> > >>> > > When we run the Test#1 for all major NICs. We found that all these>> NIC port(igb,>> > ixgbe, i40e, fm10k) can't be started. Pls check, if the patch is>> applied, all INTEL>> > port can't be start, terrible things!>> > >>> > > Interactive-mode selected>> > > Configuring Port 0 (socket 0)>> > > PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f13e99e3440>> > > hw_ring=0x7f13e99e5480 dma_addr=0x8299e5480>> > > PMD: ixgbe_set_tx_function(): Using simple tx code path>> > > PMD: ixgbe_set_tx_function(): Vector tx enabled.>> > > PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f13ffcb8080>> > > sw_sc_ring=0x7f13ffcbaac0 hw_ring=0x7f13e99d3380 dma_addr=0x8299d3380>> > > PMD: ixgbe_dev_start(): Invalid link_speeds for port 0; >> > > autonegotiation disabled Fail to start port 0 Configuring Port 1>> > > (socket 0)>> > > PMD: i40e_set_tx_function_flag(): Vector tx can be enabled on this>> txq.>> > > PMD: i40e_dev_rx_queue_setup(): Rx Burst Bulk Alloc Preconditions are>> > satisfied. Rx Burst Bulk Alloc function will be used on port=1, queue=0.>> > > PMD: i40e_dev_start(): Invalid link_speeds for port 1; autonegotiation>> > > disabled>> > >>> > >>> > > Just to double-check; is the test#1 adapted to the _new_ API that>> ethdev has>> > to set link speeds? For the output it seems autoneg is disabled =>>> fixed speed,>> > hence the new bitmaps have to be used.>> > >>> > > (I am not claiming patchset is bug free; there might be issues still)>> > >>> > > Regards>> > > marc>> > >>> > > Fail to start port 1>> > > Please stop the ports first>> > > Done>> > >>> > > Thanks>> > > Qian>> > >>> > >>> > > -----Original Message----->> > > RE: DPDK link speed with Intel devices>> > >>> > > Hi Mike,>> > >>> > > We just knew this patch set last week.>> > > Since this patch set is required to test with a lot of NIC,>> we need>> > more document from Dev about this patch.>> > > Currently, Qian is working on with Wenzhuo on it now.>> > >>> > > Waterman>> > >>> > >>> > > -----Original Message----->> > > FW: DPDK link speed with Intel devices>> > > Importance: High>> > >>> > > Hi Waterman, all>> > >>> > > See below - are you aware? And if so where are we with>> testing/resolution?>> > >>> > > Regards>> > > Mike>> > >>> > >>> > >>> > > -----Original Message----->> > >

[dpdk-test-report] [PatchWork]|SUCCESS| pw11741 ethdev: 100G and link speed>> > > API refactoring>> > >>> > > 2016-03-17 19:08, Thomas Monjalon:>> > > > There are still too few tests and reviews, especially for>> > > > autonegotiation with Intel devices (patch #6).>> > > > I would not be surprised to see some bugs in this rework.>> > >>> > > Any feedback about autoneg in e1000/ixgbe/i40e?>> > > Has it been tested before its integration in RC2?>> > >>> > > > The capabilities must be adapted per device. It can be improved in a>> > > > separate patch.>> > > >>> > > > It will be integrated in 16.04-rc2.>> > > > Please test and review shortly, thanks!>> > >>> > >>> > > ---------- Forwarded message ---------->> > > RE: DPDK link speed with Intel devices Hi, all We have worked>> > > out the basic test cases for the patchset.>> > > 1. Test the link speed on major Intel NICs to see if the speed is>> right.>> > > 2. Test the auto-negoation on major Intel NICs to ensure it's working.>> > > Nic covered: ixgbe, igb, i40e, fm10k, bonding(SW), virtio(SW)>> > >>> > > When we run the Test#1 for all major NICs. We found that all these>> NIC port(igb,>> > ixgbe, i40e, fm10k) can't be started. Pls check, if the patch is>> applied, all INTEL>> > port can't be start, terrible things!>> > >>> > > Interactive-mode selected>> > > Configuring Port 0 (socket 0)>> > > PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f13e99e3440>> > > hw_ring=0x7f13e99e5480 dma_addr=0x8299e5480>> > > PMD: ixgbe_set_tx_function(): Using simple tx code path>> > > PMD: ixgbe_set_tx_function(): Vector tx enabled.>> > > PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f13ffcb8080>> > > sw_sc_ring=0x7f13ffcbaac0 hw_ring=0x7f13e99d3380 dma_addr=0x8299d3380>> > > PMD: ixgbe_dev_start(): Invalid link_speeds for port 0; >> > > autonegotiation disabled Fail to start port 0 Configuring Port 1>> > > (socket 0)>> > > PMD: i40e_set_tx_function_flag(): Vector tx can be enabled on this>> txq.>> > > PMD: i40e_dev_rx_queue_setup(): Rx Burst Bulk Alloc Preconditions are>> > satisfied. Rx Burst Bulk Alloc function will be used on port=1, queue=0.>> > > PMD: i40e_dev_start(): Invalid link_speeds for port 1; autonegotiation>> > > disabled>> > >>> > >>> > > Just to double-check; is the test#1 adapted to the _new_ API that>> ethdev has>> > to set link speeds? For the output it seems autoneg is disabled =>>> fixed speed,>> > hence the new bitmaps have to be used.>> > >>> > > (I am not claiming patchset is bug free; there might be issues still)>> > >>> > > Regards>> > > marc>> > >>> > > Fail to start port 1>> > > Please stop the ports first>> > > Done>> > >>> > > Thanks>> > > Qian>> > >>> > >>> > > -----Original Message----->> > > RE: DPDK link speed with Intel devices>> > >>> > > Hi Mike,>> > >>> > > We just knew this patch set last week.>> > > Since this patch set is required to test with a lot of NIC,>> we need>> > more document from Dev about this patch.>> > > Currently, Qian is working on with Wenzhuo on it now.>> > >>> > > Waterman>> > >>> > >>> > > -----Original Message----->> > > FW: DPDK link speed with Intel devices>> > > Importance: High>> > >>> > > Hi Waterman, all>> > >>> > > See below - are you aware? And if so where are we with>> testing/resolution?>> > >>> > > Regards>> > > Mike>> > >>> > >>> > >>> > > -----Original Message----->> > >

[sys_stv]

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

Test-Label: Intel Niantic on Fedora
Test-Status: SUCCESS

Patchwork ID: 11741
http://www.dpdk.org/dev/patchwork/patch/11741/
Submitter: Marc Sune <marcdevel@gmail.com>
Date: Fri, 25 Mar 2016 22:30:51 +0100Tue, 22 Mar 2016 06:41:37 +0000
DPDK git baseline: 6ac91f938cc88423885b757ce24c2a984da097d4

Check patch:Success

Compilation:
OS: fedora
Nic: niantic
GCC: gcc_x86-64, 4.8.3
x86_64-native-linuxapp-gcc-combined: compile pass
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-clang: compile pass
x86_64-native-linuxapp-gcc-shared: compile pass
x86_64-native-linuxapp-gcc-debug: compile pass



DPDK STV team