VF cannot creation with large CPU core systems when RDMA enabled with intel ice driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-hwe-5.15 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Issue Environment:
==================
root@npx:~# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_
ID=ubuntu
ID_LIKE=debian
HOME_URL="https:/
SUPPORT_URL="https:/
BUG_REPORT_URL="https:/
PRIVACY_
UBUNTU_
root@npx:~# uname -r
5.15.0-88-generic
root@npx:~# lscpu | head -n 5
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 52 bits physical, 57 bits virtual
Byte Order: Little Endian
CPU(s): 256
root@npx:~# ethtool -i ens2f0
driver: ice
version: 5.15.0-88-generic
firmware-version: 4.40 0x8001c7d5 1.3534.0
expansion-
bus-info: 0000:16:00.0
supports-
supports-test: yes
supports-
supports-
supports-
root@npx:~# lspci -s 16:00.0 -vvv
16:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)
Subsystem: Intel Corporation Ethernet Network Adapter E810-XXV-4
Physical Slot: 2
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
NUMA node: 0
IOMMU group: 19
Region 0: Memory at 201ffa000000 (64-bit, prefetchable) [size=32M]
Region 3: Memory at 201ffe030000 (64-bit, prefetchable) [size=64K]
Expansion ROM at 95800000 [disabled] [size=1M]
End
VF offset: 8, stride: 1, Device ID: 1889
VF Migration: offset: 00000000, BIR: 0
No steering table available
Kernel driver in use: ice
Kernel modules: ice
Issue Description:
==================
# echo 1 > /sys/class/
[ 5734.469217] ice 0000:16:00.0: Enabling 1 VFs
[ 5734.574945] pci 0000:16:01.0: [8086:1889] type 00 class 0x020000
[ 5734.574970] pci 0000:16:01.0: enabling Extended Tags
[ 5734.575471] pci 0000:16:01.0: Adding to iommu group 443
[ 5734.575718] ice 0000:16:00.0: Only 0 MSI-X interrupts available for SR-IOV. Not enough to support minimum of 2 MSI-X interrupts per VF for 1 VFs
[ 5734.575815] ice 0000:16:00.0: Not enough resources for 1 VFs, try with fewer number of VFs
[ 5734.576861] pci 0000:16:01.0: Removing from iommu group 443
[ 5734.623292] iavf: Intel(R) Ethernet Adaptive Virtual Function Network Driver
[ 5734.623297] Copyright (c) 2013 - 2018 Intel Corporation.
[ 5735.598871] ice 0000:16:00.0: Failed to enable SR-IOV: -28
Issue Found:
============
1> After disable RDMA, the VF creation works fine; from kernel code, the MSIx are preserved by LAN and RDMA based on CPU cores, this will exhauste all available MSIx for larger core systems (some PF port will only have 512 MSIx in total), this doesn't make sense as the default value (at least make sure a few number VFs can be created successfully if NIC support it)
2> When do the MSIx resource reallocation manually, still raise below error, this is some what a strange behavior, it's better to allow such actions by default from kernel:
root@npx:~# devlink resource show pci/0000:16:00.0
kernel answers: Operation not supported
affects: | ubuntu → linux-hwe-5.15 (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/2044810/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]