> -----Original Message-----
> From: David Marchand <david.march...@redhat.com>
> Sent: Tuesday, July 28, 2020 8:05 PM
> To: Xueming(Steven) Li <xuemi...@mellanox.com>
> Cc: dev <dev@dpdk.org>; a...@dpdk.org; Maxime Coquelin
> <maxime.coque...@redhat.com>
> Subject: Re: [dpdk-dev] [v2] vdpa/mlx5: fix event queue number query
>
> On Tue, Jul 28, 2020 at 11:23 AM Xueming Li <xuemi...@mellanox.com> wrote:
> >
> > With latest rte api, vdpa example failed on vq setup, the api to get
> > event queue of specified core failed.
> >
> > After
> > commit 67ae5936c4fc36 ("eal: fix lcore accessors for non-EAL
> > threads"), code of "vhost-event" thread to get current cpu id returns -1.
> >
>
> This is how you figured this problem, but the first part of the commitlog
> gives
> the impression there is a regression in the EAL.
> I would prefer it is removed (maybe simply when applying?).
NP, sorry for the confusing.
>
>
> > On the other hand, internal api devx_query_eqn expects index of event
> > queue vectors, no need to use cpu id. As the doorbell handling thread
> > is per device, it's sufficient to use default event queue.
> >
> > This patch uses the default id(0) as event queue index.
> >
> > Fixes: 8395927cdfaf ("vdpa/mlx5: prepare HW queues")
> >
> > Signed-off-by: Xueming Li <xuemi...@mellanox.com>
> > Acked-by: Matan Azrad <ma...@mellanox.com>
>
>
> Thanks.
>
> --
> David Marchand
