[dpdk-dev] [PATCH v3] examples/l2fwd-event: add option to configure port pairs

[Jerin Jacob]

On Tue, Mar 31, 2020 at 10:37 PM Andrzej Ostruszka <amo at semihalf.com> wrote:
>
> On 3/31/20 2:53 PM, pbhagavatula at marvell.com wrote:
> > From: Pavan Nikhilesh <pbhagavatula at marvell.com>
> >
> > Current l2fwd-event application statically configures adjacent ports as
> > destination ports for forwarding the traffic.
> >
> > Add a config option to pass the forwarding port pair mapping which allows
> > the user to configure forwarding port mapping.
> >
> > If no config argument is specified, destination port map is not
> > changed and traffic gets forwarded with existing mapping.
> >
> > To align port/queue configuration of each lcore with destination port
> > map, port/queue configuration of each lcore gets modified when config
> > option is specificed.
> >
> > Ex: ./l2fwd-event -c 0xff -- -p 0x3f -q 2 --config="(0,3)(1,4)(2,5)"
> >
> > With above config option, traffic received from portid = 0 gets forwarded
> > to port = 3 and vice versa, similarly traffic gets forwarded on other port
> > pairs (1,4) and (2,5).
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula at marvell.com>
> > ---
> >  v3 Changes:
> >   - Use simple memcpy instead of snprintf. (Andrzej)
> >   - Skip redudant loop iterations. (Andrzej)
> >   - Use RTE_MAX_ETHPORTS instead of hardcoding to 255. (Andrzej)
> >
> >  v2 Changes:
> >   - Fix minor formatting error.
> >   - Change uint8_t to bool.
>
> Reviewed-by: Andrzej Ostruszka <aostruszka at marvell.com>

Applied to dpdk-next-eventdev/master. Thanks.