2021-10-05 17:44 (UTC+0530), Harman Kalra: > Making changes to the interrupt framework to use interrupt handle > APIs to get/set any field. Direct access to any of the fields > should be avoided to avoid any ABI breakage in future.
How is ABI breakage applicable to internal consumers? This protects against fields renaming for sure, but convenience is arguable. If EAL needs to add a EAL-private field to struct rte_intr_handle, it must add an accessor even though the field is likely OS-specific. It would be simpler if the definition was in some private EAL header and could be accessed directly by EAL code.
