Re: [dpdk-dev] [PATCH] doc: announce: make rte intr handle internal

2021-08-04 Thread Thomas Monjalon
> > > Moving struct rte_intr_handle as an internal structure to > > > avoid any ABI breakages in future. Since this structure defines > > > some static arrays and changing respective macros breaks the ABI. > > > Eg: > > > Currently RTE_MAX_RXTX_INTR_VEC_ID imposes a limit of maximum 512 > > > MSI-X

Re: [dpdk-dev] [PATCH] doc: announce: make rte intr handle internal

2021-08-02 Thread Jerin Jacob
gt; > Cc: dev@dpdk.org; Harman Kalra > > Subject: [dpdk-dev] [PATCH] doc: announce: make rte intr handle internal > > > > Moving struct rte_intr_handle as an internal structure to > > avoid any ABI breakages in future. Since this structure defines > > som

Re: [dpdk-dev] [PATCH] doc: announce: make rte intr handle internal

2021-08-02 Thread Xia, Chenbo
> -Original Message- > From: dev On Behalf Of Harman Kalra > Sent: Tuesday, August 3, 2021 12:04 AM > To: jer...@marvell.com; david.march...@redhat.com; tho...@monjalon.net; Ray > Kinsella > Cc: dev@dpdk.org; Harman Kalra > Subject: [dpdk-dev] [PATCH] doc: announce:

Re: [dpdk-dev] [PATCH] doc: announce: make rte intr handle internal

2021-08-02 Thread Andrew Rybchenko
On 8/2/21 7:03 PM, Harman Kalra wrote: Moving struct rte_intr_handle as an internal structure to avoid any ABI breakages in future. Since this structure defines some static arrays and changing respective macros breaks the ABI. Eg: Currently RTE_MAX_RXTX_INTR_VEC_ID imposes a limit of maximum 512

[dpdk-dev] [PATCH] doc: announce: make rte intr handle internal

2021-08-02 Thread Harman Kalra
Moving struct rte_intr_handle as an internal structure to avoid any ABI breakages in future. Since this structure defines some static arrays and changing respective macros breaks the ABI. Eg: Currently RTE_MAX_RXTX_INTR_VEC_ID imposes a limit of maximum 512 MSI-X interrupts that can be defined for