[Severity: Low]
Is U32_MAX really the largest length an mlx5 data segment can describe?
The commit message says:
TX data segments have a 32-bit byte count, so devmem TX frags don't
need a size limit.
Bit 31 of byte_count looks like it is the inline segment marker rather
than part of the length:
[..]
Would a value that matches the hardware, such as (1U << 31) - 1 or SZ_1G,
work better here? The commit message would need updating to match.
Let me switch to SZ_1G to be 100% safe.
---
pw-bot: cr