-
Notifications
You must be signed in to change notification settings - Fork 9
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
ethtool: add support for private flags #22
Conversation
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.
Seems reasonable, are there any example known flags that are common that we could document here?
We also want to make sure this builds on non-Linux, see the mac build failures. Otherwise seems good so far. |
6e1264d
to
cbdcb31
Compare
@mdlayher Added some tests based on ethtool reference values and fixed the MacOS build. |
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.
LGTM, well done.
Ah, looks like an easy fix:
|
This adds support for geting and setting private flags which are driver-specific (and sometimes even model-specific) controls not part of any generic network settings API. They are used to toggle low-level features in various NICs.
cbdcb31
to
e9c21a3
Compare
@mdlayher Fixed, now actually cross-build-tested and passing. |
This adds support for geting and setting private flags which are driver-specific (and sometimes even model-specific) controls not part of any generic network settings API.
They are used to toggle low-level features in various NICs.
There are currently no tests in this, considering the driver-specific nature of this I am not sure how to best add some. This has been experimentally tested on Linux 6.1 LTS and seems to work fine.