-
Notifications
You must be signed in to change notification settings - Fork 131
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
Do not expect or emit padded byte strings in BFRT P4Runtime translator #938
Conversation
- No need to add padding zeros when writing to the low level driver - Values from low level driver for port number can be 1 or 2 bytes
low level driver being the SDE wrapper here? Or does the SDE accept truncated strings now? |
I mean SDE accepts truncated byte strings |
Did you test the SDE with custom code? Because all translated entries still go through the wrapper, which does the padding. Either way, the wrapper will take care of it, no need to pad here. |
I was wrong, I didn't realized that the wrapper adds padding zeros before sending to the SDE |
Codecov Report
@@ Coverage Diff @@
## main #938 +/- ##
==========================================
- Coverage 79.20% 79.18% -0.02%
==========================================
Files 339 339
Lines 30928 30924 -4
==========================================
- Hits 24495 24488 -7
- Misses 6433 6436 +3
|
No worries, I wasn't sure if the SDE changed either. |
…um#938) Signed-off-by: Derek G Foster <derek.foster@intel.com>
…um#938) Signed-off-by: Derek G Foster <derek.foster@intel.com>
incompatible_enable_bfrt_legacy_bytestring_responses
to false