-
Notifications
You must be signed in to change notification settings - Fork 210
QAT Gen4 #529
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
QAT Gen4 #529
Conversation
62ac3be
to
7c504b5
Compare
The plugin now detects/accepts 4xxx and c4xxx devices too and defaults to those drivers that are part of Linux mainline. Signed-off-by: Mikko Ylinen <[email protected]>
Codecov Report
Continue to review full report at Codecov.
|
cmd/qat_plugin/dpdkdrv/dpdkdrv.go
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the order of the drivers important here? I guess
for _, vfDriver := range append(dp.kernelVfDrivers, dp.dpdkDriver) {
would be more readable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We prefer devices that are already bound to the targeted driver. See: #146
The updated dp.scan() changes the way how VF devices are detected. The main reason for the change is to take into account cases where the QAT VF driver is not present in the system at all but only the PF driver is loaded (and the SR-IOV devices are are enabled). The rework also takes into account bare metal and VM deployments and adds a test case for checking the virtualized environment. Signed-off-by: Mikko Ylinen <[email protected]>
vfdevID, err := dp.getDeviceID(vfBdf) | ||
if err != nil { | ||
klog.Warningf("Can't read sysfs for driver as Driver %s is not available: Skipping", driver) | ||
return nil, errors.Wrapf(err, "Cannot obtain device ID for %s", vfBdf) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: no need to embed one more stack trace into the error. Can be fixed in a followup PR though as the existing code in the master branch does the same.
Closes: #451