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

Update DDP docs to include E800 series #343

Merged

Conversation

martinkennelly
Copy link
Member

Update DDP README to add E800 series
Add E800 series examples

Signed-off-by: Martin Kennelly <martin.kennelly@intel.com>
Signed-off-by: Martin Kennelly <martin.kennelly@intel.com>
Signed-off-by: Martin Kennelly <martin.kennelly@intel.com>

For example, to download and extract the GTP profile:
##### DDP package applied to all physical cards on a host
Symbolically link your DDP package to the ```ice.pkg``` package in your NIC firmware folder (typically ```/lib/firmware/updates/intel/ice/ddp```/) and reload all the physical function drivers or simply reload ice driver.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"reload all the physical function drivers or simply reload ice driver" - What's the difference between reloading physical function drivers and reload ice driver? Won't physical function driver be equal to ice driver (in E800 case) ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zshi-redhat Indeed - PF Driver == ice driver.
There is no difference unless you wanted an E800 card not to be updated for some reason. I will update this.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, so you actually can unbind the driver from a particular device which doesn't affect other devices using the same driver (guess this is what you mean in the origianl statement?)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes exactly.

> Note: You can only load DDP profile into a controller using only first Physical Function(PF0).
#### Intel® Ethernet Controller X710
Please see the i40e driver readme for full details.
Use Linux `ethtool` utility to load a DDP package into the controller.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it require reloading i40e driver? (The reloading of driver is mentioned in E800 explicitly, but not for X710).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zshi-redhat No reloading of the driver required.


(ref: [Dynamic Device Personalization for Intel® Ethernet 700 Series](https://software.intel.com/en-us/articles/dynamic-device-personalization-for-intel-ethernet-700-series))
## Dynamic Device Personalization for Intel® Ethernet Controller E810
For Intel® Ethernet Controller E810, a DDP package can be loaded into the NIC using the ice kernel driver. Current device DDP state can be determined with DDPTool or devlink.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to add devlink support in sriov device plugin?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zshi-redhat Yes. It is currently being worked on by Patryk. I discussed it at the last community meeting.

Signed-off-by: Kennelly, Martin <martin.kennelly@intel.com>
@martinkennelly martinkennelly merged commit ab84f1f into k8snetworkplumbingwg:master Apr 13, 2021
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

Successfully merging this pull request may close these issues.

2 participants