RE: [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-08-02 Thread Gagandeep Singh
Hi, > -Original Message- > From: Konstantin Ananyev > Sent: Wednesday, July 24, 2024 1:32 PM > To: Konstantin Ananyev ; Gagandeep > Singh ; dev@dpdk.org; Konstantin Ananyev > ; Sean Morrissey > > Cc: sta...@dpdk.org > Subject: RE: [PATCH 3/3] examples/l3fwd:

RE: [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-07-24 Thread Konstantin Ananyev
> > > > > > > Application is accepting routes for port ID up to UINT8_MAX for > > > > > > > LPM amd EM routes on parsing the given rule file, but only up to > > > > > > > 32 ports can be enabled as per the variable enabled_port_mask > > > > > > > which is defined as uint32_t. > > > > > > > > > >

RE: [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-07-23 Thread Konstantin Ananyev
> > > > > > Application is accepting routes for port ID up to UINT8_MAX for > > > > > > LPM amd EM routes on parsing the given rule file, but only up to > > > > > > 32 ports can be enabled as per the variable enabled_port_mask > > > > > > which is defined as uint32_t. > > > > > > > > > > > > This p

RE: [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-07-21 Thread Gagandeep Singh
Hi, > > > > > Application is accepting routes for port ID up to UINT8_MAX for > > > > > LPM amd EM routes on parsing the given rule file, but only up to > > > > > 32 ports can be enabled as per the variable enabled_port_mask > > > > > which is defined as uint32_t. > > > > > > > > > > This patch r

RE: [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-07-21 Thread Gagandeep Singh
Hi, > -Original Message- > From: Konstantin Ananyev > Sent: Thursday, July 18, 2024 3:32 PM > To: Gagandeep Singh ; dev@dpdk.org; Konstantin Ananyev > ; Sean Morrissey > > Cc: sta...@dpdk.org > Subject: RE: [PATCH 3/3] examples/l3fwd: fix maximum accept

RE: [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-07-18 Thread Konstantin Ananyev
> > > Application is accepting routes for port ID up to UINT8_MAX for LPM > > > amd EM routes on parsing the given rule file, but only up to 32 ports > > > can be enabled as per the variable enabled_port_mask which is defined > > > as uint32_t. > > > > > > This patch restricts the rules parsing

RE: [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-07-17 Thread Gagandeep Singh
Hi, > -Original Message- > From: Konstantin Ananyev > Sent: Wednesday, July 17, 2024 3:48 PM > To: Gagandeep Singh ; dev@dpdk.org; Konstantin Ananyev > ; Sean Morrissey > > Cc: sta...@dpdk.org > Subject: RE: [PATCH 3/3] examples/l3fwd: fix maximum accept

RE: [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-07-17 Thread Konstantin Ananyev
> Application is accepting routes for port ID up to UINT8_MAX > for LPM amd EM routes on parsing the given rule file, but only > up to 32 ports can be enabled as per the variable enabled_port_mask > which is defined as uint32_t. > > This patch restricts the rules parsing code to accept routes f

[PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes

2024-07-15 Thread Gagandeep Singh
Application is accepting routes for port ID up to UINT8_MAX for LPM amd EM routes on parsing the given rule file, but only up to 32 ports can be enabled as per the variable enabled_port_mask which is defined as uint32_t. This patch restricts the rules parsing code to accept routes for port ID up t