One more info.
This issue is not observed by PF directly but can be observed by VFs.
I am blocked by this error. May I get some help about this issue? Thanks a lot.
At 2021-04-08 22:46:37, "vdf" <thomas200...@163.com> wrote:
>Actually, the Jumbo frame is enanbled during . What could be the reason for
>failure to set max package length to 9600 bytes?
> struct rte_eth_rxmode rxmode =
> { .split_hdr_size = 0,
> .max_rx_pkt_len = MAX_RX_LEN,
> .offloads=(DEV_RX_OFFLOAD_JUMBO_FRAME
> /*|DEV_RX_OFFLOAD_CRC_STRIP*/)
> };
>
>
>
>
>
>At 2021-04-08 00:06:06, "vdf" <thomas200...@163.com> wrote:
>>Hi all,
>>
>>
>>I have already set up 2 VFs on enslf1 NIC. The DPDK version is
>>dpdk-stable-19.11.7. There is one issue related to max packet length to 9600.
>>I tried both igb_uio and VFIO_PCI as driver. Could you kindly guide me how to
>>fix this issue?
>>
>>
>>#ens1f1 setting
>>5: ens1f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
>>DEFAULT group default qlen 1000
>> link/ether f8:f2:1e:13:e0:9d brd ff:ff:ff:ff:ff:ff
>> vf 0 MAC 00:11:22:33:44:55, vlan 2, spoof checking on, link-state auto,
>> trust off, query_rss off
>> vf 1 MAC 00:11:22:33:44:55, vlan 1, spoof checking on, link-state auto,
>> trust off, query_rss off
>>#ens1f1 profile
>> ethtool -i ens1f1
>>driver: ixgbe
>>version: 5.1.0-k
>>firmware-version: 0x00015e0b
>>expansion-rom-version:
>>bus-info: 0000:03:00.1
>>supports-statistics: yes
>>supports-test: yes
>>supports-eeprom-access: yes
>>supports-register-dump: yes
>>supports-priv-flags: yes
>>
>>
>>#issue I met
>>EAL: Selected IOVA mode 'PA'
>>
>>EAL: Probing VFIO support...
>>
>>EAL: VFIO support initialized
>>
>>EAL: PCI device 0000:03:10.1 on NUMA socket 0
>>
>>EAL: probe driver: 8086:10ed net_ixgbe_vf
>>
>>EAL: using IOMMU type 1 (Type 1)
>>
>>initializing port 0 for TX, drv=net_ixgbe_vf
>>
>>Port 0 MAC: 00 11 22 33 44 55
>>
>>Port 0: nb_rxd 4096 nb_txd 4096
>>
>>ixgbevf_dev_rx_init(): Set max packet length to 9600 failed.
>>
>>ixgbevf_dev_start(): Unable to initialize RX hardware (-22)
>>
>>
>>
>>Thanks,
>>Thomas.
>>
>>
>>
>>
