Oracle Confidential Hi Dariusz,
I noticed that this patch was later reverted by: > net/mlx5: revert fallback to Verbs Tx allocation The revert mentions that on Windows, DevX CQ creation was failing due to a different allocation fallback behavior. Could you please clarify what specific behavior needs to be addressed for Windows? Should the original fallback be reworked to handle the Windows case, or should the fallback be avoided entirely when running on Windows? I would like to understand the expected behavior so I can work on a correct fix. Thanks, Banoth Saikumar Oracle Confidential ________________________________ From: Dariusz Sosnowski <[email protected]> Sent: 13 July 2026 16:45 To: Banoth Saikumar <[email protected]> Cc: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: [External] : Re: [PATCH v2] net/mlx5: fallback to verbs for Tx memory allocation if devx unsupported On Tue, Jun 30, 2026 at 03:53:11PM +0530, [email protected] wrote: > From: Banoth Saikumar <[email protected]> > > Previously, the mlx5 PMD attempted to allocate consecutive Tx memory > using DevX without checking whether the NIC actually supported DevX. > This led to allocation failures on legacy or unsupported NICs. > > This patch adds a fallback mechanism: if DevX is not available, the PMD > skips DevX-based allocation and allows the verbs path to handle memory > allocation and registration. This improves compatibility with older > NICs and ensures Tx queue setup proceeds correctly. > > Fixes: bbfab2eb2528 ("net/mlx5: allocate and release unique > resources for Tx queues") > Cc: [email protected] > > Signed-off-by: Banoth Saikumar <[email protected]> Acked-by: Dariusz Sosnowski <[email protected]>
