Hello Thomas,

My sincere apologies for the delayed response and for continuing to submit patches without answering your questions first. I did not mean to ignore the discussion, and I appreciate your patience.

To answer your question regarding our plans for common/sxe2:

We do not currently plan to add other driver classes like crypto or compress. However, the common/sxe2 directory was introduced to host our hardware abstraction layer (HAL) and base code, with the strategic goal of code reuse for future generations of our network interface cards (e.g., sxe3, sxe4, etc.).

This base code handles general hardware initialization, register maps, and management structures that will remain consistent and shared across our upcoming chip iterations, rather than being specific only to the current sxe2 ethdev logic.

That being said, we want to align with DPDK's upstream policies. If the community prefers to keep all net-only driver code within the net directory until a multi-class or multi-generation need officially arrives in the upstream, I am fully open to refactoring the patches. I can merge the common/sxe2 logic entirely into drivers/net/sxe2 for this release.

Please let me know your thoughts on this approach, and I will wait for your guidance before sending the next version.

Best regards,
Liu Jie