RE: [RFC v4 0/8] Symbol versioning and export rework

2025-03-26 Thread Morten Brørup
> From: David Marchand [mailto:david.march...@redhat.com] > Sent: Wednesday, 26 March 2025 13.03 > [...] > And I don't see symbol versioning as a MUST infrastructure that DPDK > needs to provide to datapath applications. Agree. Getting rid of the exotic stuff like symbol versioning would make t

Re: [RFC v4 0/8] Symbol versioning and export rework

2025-03-26 Thread David Marchand
On Wed, Mar 26, 2025 2:37 PM Bruce Richardson wrote: > > - I am considering making rte_function_versioning.h a non exported > > header (precisely, moving it to buildtools/ and maybe renaming it). > > > > This header contains macros not prefixed with RTE_. > > Using it requires some build trick (se

Re: [RFC v4 0/8] Symbol versioning and export rework

2025-03-26 Thread David Marchand
On Mon, Mar 17, 2025 at 4:43 PM David Marchand wrote: > > So far, each DPDK library (or driver) exposing symbols in an ABI had to > maintain a version.map and use some macros for symbol versioning, > specially crafted with the GNU linker in mind. > > This series proposes to rework the whole princi

Re: [RFC v4 0/8] Symbol versioning and export rework

2025-03-26 Thread Bruce Richardson
On Wed, Mar 26, 2025 at 02:54:32PM +0100, David Marchand wrote: > On Wed, Mar 26, 2025 2:37 PM Bruce Richardson > wrote: > > > - I am considering making rte_function_versioning.h a non exported > > > header (precisely, moving it to buildtools/ and maybe renaming it). > > > > > > This header contai

Re: [RFC v4 0/8] Symbol versioning and export rework

2025-03-26 Thread Bruce Richardson
On Wed, Mar 26, 2025 at 01:02:32PM +0100, David Marchand wrote: > On Mon, Mar 17, 2025 at 4:43 PM David Marchand > wrote: > > > > So far, each DPDK library (or driver) exposing symbols in an ABI had to > > maintain a version.map and use some macros for symbol versioning, > > specially crafted with

Re: [RFC v4 0/8] Symbol versioning and export rework

2025-03-26 Thread Bruce Richardson
On Wed, Mar 26, 2025 at 01:02:32PM +0100, David Marchand wrote: > On Mon, Mar 17, 2025 at 4:43 PM David Marchand > wrote: > > > > So far, each DPDK library (or driver) exposing symbols in an ABI had to > > maintain a version.map and use some macros for symbol versioning, > > specially crafted with

Re: [RFC v4 0/8] Symbol versioning and export rework

2025-03-18 Thread David Marchand
On Mon, Mar 17, 2025 at 4:43 PM David Marchand wrote: > > So far, each DPDK library (or driver) exposing symbols in an ABI had to > maintain a version.map and use some macros for symbol versioning, > specially crafted with the GNU linker in mind. > > This series proposes to rework the whole princi

[RFC v4 0/8] Symbol versioning and export rework

2025-03-17 Thread David Marchand
So far, each DPDK library (or driver) exposing symbols in an ABI had to maintain a version.map and use some macros for symbol versioning, specially crafted with the GNU linker in mind. This series proposes to rework the whole principle, and instead rely on marking the symbol exports in the source