Re: [dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-21 Thread David Marchand
On Tue, Oct 19, 2021 at 9:09 PM Aaron Conole wrote: > > David Marchand writes: > > > Cores count has a direct impact on the time needed to complete unit > > tests. > > > > Currently, the core list used for unit test is enforced to "all cores on > > the system" with no way for (CI) users to adapt

Re: [dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-20 Thread David Marchand
On Tue, Oct 19, 2021 at 9:28 PM David Marchand wrote: > The other three warnings (all of them about "test-args") are > introduced by this patch, and this is a problem: once merged, I > understand any following patch will get flagged as failing this check. > There may be something better to do for

Re: [dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-19 Thread David Marchand
On Tue, Oct 19, 2021 at 9:09 PM Aaron Conole wrote: > > David Marchand writes: > > > Cores count has a direct impact on the time needed to complete unit > > tests. > > > > Currently, the core list used for unit test is enforced to "all cores on > > the system" with no way for (CI) users to adapt

Re: [dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-19 Thread Aaron Conole
David Marchand writes: > Cores count has a direct impact on the time needed to complete unit > tests. > > Currently, the core list used for unit test is enforced to "all cores on > the system" with no way for (CI) users to adapt it. > On the other hand, EAL default behavior (when no -c/-l option

Re: [dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-19 Thread Honnappa Nagarahalli
> > > > > > > > Cores count has a direct impact on the time needed to complete unit tests. > > We also need to control the number of iterations with in the tests. > > > > We could add something like "-i low/medium/high". The test cases then can > use this to decide on how many iterations to run.

Re: [dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-19 Thread David Marchand
On Tue, Oct 19, 2021 at 4:46 PM Honnappa Nagarahalli wrote: > > > > > > > Cores count has a direct impact on the time needed to complete unit tests. > We also need to control the number of iterations with in the tests. > > We could add something like "-i low/medium/high". The test cases then can

Re: [dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-19 Thread Honnappa Nagarahalli
> > Cores count has a direct impact on the time needed to complete unit tests. We also need to control the number of iterations with in the tests. We could add something like "-i low/medium/high". The test cases then can use this to decide on how many iterations to run. > > Currently, the co

Re: [dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-19 Thread Bruce Richardson
On Tue, Oct 19, 2021 at 01:26:02PM +0200, David Marchand wrote: > Cores count has a direct impact on the time needed to complete unit > tests. > > Currently, the core list used for unit test is enforced to "all cores on > the system" with no way for (CI) users to adapt it. > On the other hand, EAL

[dpdk-dev] [PATCH v2] test: rely on EAL detection for core list

2021-10-19 Thread David Marchand
Cores count has a direct impact on the time needed to complete unit tests. Currently, the core list used for unit test is enforced to "all cores on the system" with no way for (CI) users to adapt it. On the other hand, EAL default behavior (when no -c/-l option gets passed) is to start threads on