add driver start callback API #740
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mtfriesen
added
feature request
csujedihy
approved these changes
Nov 13, 2024
|
What's the plan for unload/stop? |
The current strategy is the same as user mode, because they share the IO manager: anything dependent on XDP must be stopped before XDP will stop. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Describe the purpose of and changes within this Pull Request.
Add a driver start callback API. This callback will be invoked each time the XDP driver has been started.
Testing
Do any existing tests cover this change? Are new tests needed?
CI for callback producer.
Documentation
Is there any documentation impact for this change?
This API will remain undocumented.
Installation
Is there any installer impact for this change?
No.