Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Intel E810 Network Adapter PF id: 1591 as supported device for SR-IOV #329

Closed
novacain1 opened this issue Jun 24, 2022 · 1 comment
Closed

Comments

@novacain1
Copy link
Contributor

Hello, requesting to add a new NIC. First time contributor here.
I'm opening this Github issue per the instructions (https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/master/doc/supported-hardware.md):

Model: Intel Corporation Ethernet Controller E810-C for backplane
Vendor: 8086
Device: 1591

Platform testing was done on a well known kubernetes platform based on 1.23. It was also tested on the same platform based on 1.21.

$ kubectl get node du4-ldc1 -o json | jq '.status.allocatable'
{
  "cpu": "56",
  "ephemeral-storage": "999669060Ki",
  "hugepages-1Gi": "16Gi",
  "hugepages-2Mi": "0",
  "memory": "113174728Ki",
  "openshift.io/vran_netdevice": "4",
  "openshift.io/vran_netdevice_fh": "2",
  "openshift.io/vran_vfio": "2",
  "pods": "250"
}
$ kubectl get sriovnetworknodestates.sriovnetwork.openshift.io du4-ldc1 -o yaml
...
  - Vfs:
    - deviceID: "1889"
      driver: iavf
      mac: 76:d5:66:9b:99:ca
      mtu: 1500
      name: enp81s0f3v0
      pciAddress: 0000:51:0d.0
      vendor: "8086"
      vfID: 0
    - deviceID: "1889"
      driver: iavf
      mac: 4e:aa:ac:c4:0f:89
      mtu: 1500
      name: enp81s0f3v1
      pciAddress: 0000:51:0d.1
      vendor: "8086"
      vfID: 1
    - deviceID: "1889"
      driver: iavf
      mac: 32:cc:d9:3f:60:1e
      mtu: 1500
      name: enp81s0f3v2
      pciAddress: 0000:51:0d.2
      vendor: "8086"
      vfID: 2
    ...
    deviceID: "1591"
    driver: ice
    eSwitchMode: legacy
    linkSpeed: 10000 Mb/s
    linkType: ETH
    mac: 00:e0:ed:f0:20:67
    mtu: 1500
    name: enp81s0f3
    numVfs: 10
    pciAddress: "0000:51:00.3"
    totalvfs: 32
    vendor: "8086"

Pod with Netdevice VF being consumed from the host perspective:

$ ip link show enp81s0f3
10: enp81s0f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 00:e0:ed:f0:20:67 brd ff:ff:ff:ff:ff:ff
    vf 0     link/ether 76:d5:66:9b:99:ca brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1     link/ether 4e:aa:ac:c4:0f:89 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2     link/ether 32:cc:d9:3f:60:1e brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3     link/ether da:65:fd:a2:40:29 brd ff:ff:ff:ff:ff:ff, vlan 806, spoof checking on, link-state auto, trust off
    vf 4     link/ether 8a:aa:b7:81:6c:e3 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 5     link/ether c6:85:15:59:89:7f brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 6     link/ether da:57:55:df:f4:29 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 7     link/ether 42:8f:66:76:69:be brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 8     link/ether e2:3a:37:ab:0a:f7 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 9     link/ether aa:94:b0:d2:cd:3c brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off

$ dmesg
...
[534307.844306] ice 0000:51:00.3: Setting VLAN 806, QoS 0x0 on VF 3
[534307.851279] iavf 0000:51:0d.3: Reset indication received from the PF
[534307.858510] iavf 0000:51:0d.3: Scheduling reset task
[534307.879440] iavf 0000:51:0d.3 temp_36: renamed from enp81s0f3v3
[534307.904390] iavf 0000:51:0d.3 net1: renamed from temp_36
...

Vendor support will be Intel, who's already added to vendor-support.md

Also, current PR is #326 .

@adrianchiris
Copy link
Collaborator

PR to add support was merged. closing this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants