Hi Sean,

> -----Original Message-----
> From: Sean Zhang (Networking SW) <xiazh...@nvidia.com>
> Sent: Wednesday, October 13, 2021 10:44 AM
> To: NBU-Contact-Thomas Monjalon <tho...@monjalon.net>; Wisam
> Monther <wis...@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasl...@nvidia.com>
> Subject: [V2] app/flow-perf: add destination ports parameter
> 
> Add optional destination ports parameter for port-id action.
> The parameter is not must, and the value is 1 by default as before if the
> parameter not provided.
> 
> For example:
> 
> $ dpdk-test-flow-perf -w 08:00.0,representor=[0,1] -- --transfer \
> > --ingress --transfer --ether --portmask=0x2 --vxlan-encap \
> > --port-id=0
> 
> This command means the rule created on representor 0 with port 0 as
> destination, since the portmask is 0x2 and dst-ports is 0:
> 
> $ dpdk-test-flow-perf -w 08:00.0,representor=[0,1] \
> > -w 08:00.1,representor=[0,1]-- --transfer --ingress --transfer \
> > --ether --portmask=0x12 --vxlan-encap --port-id=0,3
> 
> This command means the rules created on both representor 0 of PF 0 and PF
> 1, the destination port for the first represontor is PF 0, and the destination
> port for the other one it PF 1.
> 
> Signed-off-by: Sean Zhang <xiazh...@nvidia.com>
> ---
> v2:
> remove new added dst-ports parameter, reuse port-id with optional
> parameter
> ---

Reviewed-by: Wisam Jaddo <wis...@nvidia.com>

BRs,
Wisam Jaddo

Reply via email to