> -----Original Message-----
> From: Stephen Hemminger <step...@networkplumber.org>
> Sent: Sunday, October 13, 2024 6:21 AM
> To: Ye, MingjinX <mingjinx...@intel.com>
> Cc: dev@dpdk.org; sta...@dpdk.org
> Subject: Re: [PATCH v2] test: fix option block
>
> On Sat, 12 Oct 2024 09:35:19 +0000
> Mingjin Ye <mingjinx...@intel.com> wrote:
>
> > The options allow (-a) and block (-b) cannot be used at the same time.
> > Therefore, allow (-a) will not be added when block (-b) is present.
> >
> > Fixes: b3ce7891ad38 ("test: fix probing in secondary process")
> > Cc: sta...@dpdk.org
> >
> > Signed-off-by: Mingjin Ye <mingjinx...@intel.com>
> > ---
>
> What is this patch trying to solve?
Solve the issue of allow/block devices being added accidentally.
The v3 patch will be sent.
>
> Right now starting dpdk-test with both options together causes an error in
> EAL init.
EAL does not support adding both allow (-a) and block (-b) options.
>
> root@hermes:/home/shemminger/DPDK/main# ./build/app/dpdk-test -a
> ae:00.0 -b 00:1f.6
> EAL: Detected CPU lcores: 8
> EAL: Detected NUMA nodes: 1
> EAL: Options allow (-a) and block (-b) can't be used at the same time
>
> Usage: ./build/app/dpdk-test [options]
>
> Therefore it should never get into the process_dup function at all.
