On 4/5/20 5:52 AM, vattun...@marvell.com wrote: > From: Vamsi Attunuru <vattun...@marvell.com> > > Current l2fwd application configures adjacent ports as destination > ports for forwarding the traffic which is a kind of static mapping > that can not be altered by the command line options. > > Patch adds a config option to pass the forwarding port pair mapping > as a command line parameter which allows the user to pass required > forwarding port mapping. > > If no config argument is specified, destination port map is not > changed and traffic gets forwarded with existing mapping. > > When port pair mapping is passed in config option, destination port map > is configured and traffic gets forwarded accordingly. > > Ex: ./l2fwd -c 0xff -- -p 0x3f --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: Vamsi Attunuru <vattun...@marvell.com> > --- > V2 Changes: > > * Fix command option format in docs. > * Use memcpy instead of snprintf. > * Rephrase if-else condition. > > doc/guides/rel_notes/release_20_05.rst | 6 + > .../sample_app_ug/l2_forward_real_virtual.rst | 18 ++- > examples/l2fwd/main.c | 169 > ++++++++++++++++++--- > 3 files changed, 172 insertions(+), 21 deletions(-)
Acked-by: Andrzej Ostruszka <aostrus...@marvell.com>
