[dpdk-dev] [PATCH 1/2] eal: make max interrupt vector id configurable
David Marchand
david.marchand at redhat.com
Wed Mar 24 12:14:59 CET 2021
On Wed, Mar 24, 2021 at 12:01 PM Jerin Jacob <jerinjacobk at gmail.com> wrote:
>
> On Fri, Feb 26, 2021 at 12:31 AM <pbhagavatula at marvell.com> wrote:
> >
> > From: Pavan Nikhilesh <pbhagavatula at marvell.com>
> >
> > Make RTE_MAX_RXTX_INTR_VEC_ID configurable as MSI-X support a
> > maximum of 2048 vectors.
> > The default value is unchanged and set to 512.
>
>
> IMO, We dont need to make it configurable and each platform sets its
> value. That scheme won't work as generic distribution build will fail
> to run.
> Since PCIe specification defines this value and there is no
> performance impact on increasing this,
> IMO, We can change to 2048 as default.
It probably breaks rte_intr_* ABI.
struct rte_intr_handle {
...
int efds[RTE_MAX_RXTX_INTR_VEC_ID]; /**< intr vectors/efds mapping */
struct rte_epoll_event elist[RTE_MAX_RXTX_INTR_VEC_ID];
/**< intr vector epoll event */
...
I see you need this for octeontx2, so wondering if you could handle
this differently in octeontx2 drivers?
--
David Marchand
More information about the dev
mailing list