[dpdk-users] xl710 NIC doesn't receive 1518 bytes packets

[Alex Kiselev]

Hi Kyle.

2018-01-26 16:47 GMT+03:00 Kyle Larose <klarose at sandvine.com>:
> I meant to suggest that, sorry. :(
>
> That said, I think a patch was submitted recently to set the mtu of slave ports when the bond's mtu is set.
>
> http://dpdk.org/browse/dpdk/commit/drivers/net/bonding/rte_eth_bond_pmd.c?id=55b58a7374554cd1c86f4a13a0e2f54e9ba6fe4d
>
> Are you running with that patch?

No. I wasn't aware of this patch.
I'll try it. Thanks.

>
>> -----Original Message-----
>> From: Alex Kiselev [mailto:kiselev99 at gmail.com]
>> Sent: Friday, January 26, 2018 8:44 AM
>> To: Kyle Larose
>> Cc: users
>> Subject: Re: [dpdk-users] xl710 NIC doesn't receive 1518 bytes packets
>>
>> 2018-01-24 17:14 GMT+03:00 Alex Kiselev <kiselev99 at gmail.com>:
>> > Hi Kyle.
>> >
>> > 2018-01-24 17:01 GMT+03:00 Kyle Larose <klarose at sandvine.com>:
>> >> Did you set the MTU on the bond port? It has separate configuration IIRC.
>>
>> I don't see any special API functions for setting MTU of a bonding port
>> neither in 17.08.1 that I am currently using nor in the latest DPDK branch.
>>
>> So, I use regular MTU setting function rte_eth_dev_set_mtu() for my bond
>> port created via command line arguments.
>> And It doesn't work. 1518 bytes packets are being filtered.
>>
>> I tried to hardcode setting MTU for each slave port and it solved the
>> problem. So, it looks like the problem is the rte_eth_dev_set_mtu() call
>> that doesn't change MTU of slave ports when it is called for a bonding port.
>>
>> The described problem exists at least with i40e driver and doesn't show up
>> when I use x520 NICS.
>>
>> --
>> Alex Kiselev



-- 
--
Kiselev Alexander