[RHEL-22354] Preparation PR for NBL chain series #1345
Conversation
Signed-off-by: Yuri Benditovich <[email protected]>
Signed-off-by: Yuri Benditovich <[email protected]>
When the device has one queue we do not need to analyze the hash and send NBLs one by one. Signed-off-by: Yuri Benditovich <[email protected]>
Signed-off-by: Yuri Benditovich <[email protected]>
This feature is disabled in production, we just fix the compilation problems when it is enabled. Signed-off-by: Yuri Benditovich <[email protected]>
Move the last TX completion timestamp from per-adapter context to per-queue context for better visibility. Signed-off-by: Yuri Benditovich <[email protected]>
Note that this is unsafe method and the result can be used only for information / tracking, not for decisions. Signed-off-by: Yuri Benditovich <[email protected]>
Signed-off-by: Yuri Benditovich <[email protected]>
If one NB failed, the entire NBL is not send, so we need to reflect this in TX errors. Also adding printout in such a case. Signed-off-by: Yuri Benditovich <[email protected]>
If defined (by default disabled by compilation) we keep the NBL history in the CNBL as a list of events. Especially useful for stuck NBL that has not completed. From the dump we'll be able to read the history. Signed-off-by: Yuri Benditovich <[email protected]>
|
Win10: BSOD on RSS test assertion "pCurrentNetBufferList", no surprise |
|
@ybendito 2025 - strict property validation failed unexpectedly, this env was updated. There is no log in the HLKX package for some reason. |
@kostyanf14 sorry, please clarify - is there still a failure of NicStrict test after update? |
Yes, for some reason wtl log was missing, so HLK marked test as failed. Rerun pass |
|
@ybendito merged |
This PR is a collection of minor changes and instrumentations taken out from development branch related to support for NBL chains completion for easier review