> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monja...@6wind.com]
> Sent: Tuesday, February 14, 2017 5:29 AM
> To: Zhang, Qi Z
> Cc: dev@dpdk.org; Wu, Jingjing
> Subject: Re: [PATCH] eal: fix max number of interrupt request
>
> 2017-02-13 01:16, Zhang, Qi Z:
> > Hi Thomas
2017-02-13 01:16, Zhang, Qi Z:
> Hi Thomas:
>
> From: Thomas Monjalon [mailto:thomas.monja...@6wind.com]
> > 2017-02-09 14:59, Qi Zhang:
> > > The max number of interrupt request is possible be changed after
> > > rte_intr_callback_register, so in get_max_intr, we need to check if
> > > nessesary
Hi Thomas:
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monja...@6wind.com]
> Sent: Friday, February 10, 2017 6:19 PM
> To: Zhang, Qi Z
> Cc: dev@dpdk.org; Wu, Jingjing
> Subject: Re: [PATCH] eal: fix max number of interrupt request
>
> 2017-02-09 14:59, Qi Zhang:
> > The
2017-02-09 14:59, Qi Zhang:
> The max number of interrupt request is possible
> be changed after rte_intr_callback_register, so
> in get_max_intr, we need to check if nessesary to
> update the max_intr.
So you are using rte_intr_enable() to update the max_intr field
in the case of VFIO_MSIX.
What
The max number of interrupt request is possible
be changed after rte_intr_callback_register, so
in get_max_intr, we need to check if nessesary to
update the max_intr.
Signed-off-by: Qi Zhang
---
lib/librte_eal/linuxapp/eal/eal_interrupts.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/li
5 matches
Mail list logo