Re: [dpdk-dev] [PATCH] test/eal: check invalid cpu value

2020-07-20 Thread Kevin Traynor
On 09/07/2020 00:04, Lukasz Wojciechowski wrote: > > W dniu 12.06.2020 o 14:09, Kevin Traynor pisze: >> When using --lcores option, CPU_SETSIZE allows a range of >> 0-1023. Check it is not being exceeded. >> >> Signed-off-by: Kevin Traynor >> --- >> app/test/test_eal_flags.c | 6 +- >> 1 f

[dpdk-dev] [PATCH] test/eal: check invalid cpu value

2020-07-20 Thread Kevin Traynor
When using --lcores option, there is a limit of CPU_SETSIZE. Currently that allows 0..1023 on Linux. Check it is caught when this limit is exceeded. Signed-off-by: Kevin Traynor --- app/test/test_eal_flags.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/app/test/test_e

Re: [dpdk-dev] [PATCH] test/eal: check invalid cpu value

2020-07-08 Thread Lukasz Wojciechowski
W dniu 12.06.2020 o 14:09, Kevin Traynor pisze: > When using --lcores option, CPU_SETSIZE allows a range of > 0-1023. Check it is not being exceeded. > > Signed-off-by: Kevin Traynor > --- > app/test/test_eal_flags.c | 6 +- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git

[dpdk-dev] [PATCH] test/eal: check invalid cpu value

2020-06-12 Thread Kevin Traynor
When using --lcores option, CPU_SETSIZE allows a range of 0-1023. Check it is not being exceeded. Signed-off-by: Kevin Traynor --- app/test/test_eal_flags.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/app/test/test_eal_flags.c b/app/test/test_eal_flags.c index 4ee809