qat.intel.com/generic resources exposed on Xeon Gold 6438Y+ despite dev_cfg being populated

[Feelas]

We're trying to understand what we should expect from the Xeon Gold 6438Y+ processors in terms of qat.intel.com resources exposed on nodes. This specific CPU uses PCI IDs for PF: 8086:4942 & for VF: 8086:4943.

Is it expected to see separate qat.intel.com/cy & qat.intel.com/dc endpoints OR should we use qat.intel.com/generic on these CPUs? This is with the assumption that the dev_cfg used looks like the one below.

[core@worker7 ~]$ sudo cat /sys/kernel/debug/qat_4xxx_0000:76:00.0/dev_cfg
[GENERAL]
ServicesEnabled = sym;asym

In other words, I understand that qat.intel.com/cy resources should be exposed with this config but qat.intel.com/generic are exposed instead.

I can see that 4941 is the only VF PCI ID present in "devicesWithCapabilities" variable in cmd/qat_plugin/dpdkdrv.go, so that might have been left by an accident (and because of that the discovery logic isn't working for 4943?). Refering specifically to PR #946

It is confusing that two Gen4 types might be behaving differently (some as cy/dc vs generic on others) so a clarification would be much appreciated :)

[mythi]

I can see that 4941 is the only VF PCI ID present in "devicesWithCapabilities" variable in cmd/qat_plugin/dpdkdrv.go, so that might have been left by an accident (and because of that the discovery logic isn't working for 4943?)

Right, this seems to be the problem. I will fix it asap.

[mythi]

@Feelas submitted #1434, hopefully merge on Wed