[dpdk-dev] [PATCH v3 03/11] examples/l3fwd: add event device configuration

Jerin Jacob jerinjacobk at gmail.com
Tue Jan 21 09:51:24 CET 2020


On Sat, Jan 11, 2020 at 7:18 PM <pbhagavatula at marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula at marvell.com>
>
> Add event device configuration based on the capabilities of the
> probed event device.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula at marvell.com>

Looks like it has a similar bug[1] that has been found in l2fwd-event.
If so, please fix it.

[1]
commit 345a22d5ec1ab70e9d965ae50558049e6c0f2f8d
Author: Pavan Nikhilesh <pbhagavatula at marvell.com>
Date:   Fri Dec 20 19:57:41 2019 +0530

    examples/l2fwd-event: fix event device config

    Always enable implicit release since we don't support explicit release
    in datapath.
    Master lcore is used only for printing stats so don't allocate event
    port for it.
    Fix service launch for event device without distributed scheduling.

    Fixes: bcb6f841d42a ("examples/l2fwd-event: setup service core")
    Cc: stable at dpdk.org

    Signed-off-by: Pavan Nikhilesh <pbhagavatula at marvell.com>
> ---
>  examples/l3fwd/l3fwd_event.c               |  3 +
>  examples/l3fwd/l3fwd_event.h               | 36 ++++++++++
>  examples/l3fwd/l3fwd_event_generic.c       | 75 ++++++++++++++++++++-
>  examples/l3fwd/l3fwd_event_internal_port.c | 78 +++++++++++++++++++++-
>  4 files changed, 190 insertions(+), 2 deletions(-)
>


More information about the dev mailing list