DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ye, MingjinX" <mingjinx.ye@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] test: fix option block
Date: Mon, 14 Oct 2024 10:22:44 +0000	[thread overview]
Message-ID: <LV3PR11MB8601DEE42606A257E384724BE5442@LV3PR11MB8601.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20241012152055.0ed85c3f@hermes.local>



> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Sunday, October 13, 2024 6:21 AM
> To: Ye, MingjinX <mingjinx.ye@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: Re: [PATCH v2] test: fix option block
> 
> On Sat, 12 Oct 2024 09:35:19 +0000
> Mingjin Ye <mingjinx.ye@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: stable@dpdk.org
> >
> > Signed-off-by: Mingjin Ye <mingjinx.ye@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.

  reply	other threads:[~2024-10-14 10:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  9:46 [PATCH] " Mingjin Ye
2024-03-15  6:49 ` Jiale, SongX
     [not found] ` <LV3PR11MB8601B4FC344CC7102C5AC010E5DD2@LV3PR11MB8601.namprd11.prod.outlook.com>
2024-07-03 14:35   ` Stokes, Ian
2024-07-04  8:09     ` Ye, MingjinX
2024-07-04 12:02       ` Stokes, Ian
2024-07-05  1:38         ` Ye, MingjinX
2024-07-10  9:02           ` Stokes, Ian
2024-10-07 17:02 ` Stephen Hemminger
2024-10-12  9:35 ` [PATCH v2] " Mingjin Ye
2024-10-12 22:20   ` Stephen Hemminger
2024-10-14 10:22     ` Ye, MingjinX [this message]
2024-10-14 10:00   ` [PATCH v3] test: fix option devices Mingjin Ye
2024-10-15 16:21     ` Stephen Hemminger
2024-10-16  8:17     ` [PATCH v4] " Mingjin Ye
2024-10-17  2:31       ` Jiale, SongX

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=LV3PR11MB8601DEE42606A257E384724BE5442@LV3PR11MB8601.namprd11.prod.outlook.com \
    --to=mingjinx.ye@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).