From: "Kaur, Arshdeep" <arshdeep.kaur@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Ben Magistro <koncept1@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [RFT] dumpcap: add file-prefix option
Date: Mon, 19 Sep 2022 11:19:59 +0000 [thread overview]
Message-ID: <DM6PR11MB3737B0B7C327638D5F493B55F04D9@DM6PR11MB3737.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220916083508.62e44c3a@hermes.local>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Friday, September 16, 2022 9:05 PM
> To: Ben Magistro <koncept1@gmail.com>
> Cc: Kaur, Arshdeep <arshdeep.kaur@intel.com>; dev@dpdk.org
> Subject: Re: [RFT] dumpcap: add file-prefix option
>
> On Fri, 16 Sep 2022 08:51:59 -0400
> Ben Magistro <koncept1@gmail.com> wrote:
>
> > Kaur,
> >
> > I believe parse_opts() should be called before dpdk_init() now see
> > https://patches.dpdk.org/project/dpdk/patch/20220125032545.7704-1-
> konc
> > ept1@gmail.com/
>
> Correct, in main branch parse_opts is before dpdk_init
Hi Stephen and Ben. I have a doubt regarding this. According to me if dpdk_init is called after parse_opts, then some caller functions (called from within parse_opts) are affected.
Eg. 1) Parameter 'D' : { "list-interfaces", no_argument, NULL, 'D' }, does not give any output.
2) Parameter 'i' : { "interface", required_argument, NULL, 'i' }, does not behave properly.
I think the reason is that port list is available after eal init. Dumpcap(secondary process) will inherit the ports used by primary process.
This implies that dpdk_init should be called before parse_opts.
But then for multiprocess support, primary process is to be picked up by providing a file-prefix (Added in parse_opts).
This implies that parse_opts should be called before dpdk_init.
So according to me there was a deadlock situation here. Which I handled by providing file-prefix input to the program before dpdk_init manually. And then after dpdk_init, parse_opts should be called.
Please let me know if I am going in the wrong direction. And how else can we solve this?
NOTE: There is a bug in 'if' condition of select_interface function. Control should enter the 'if' condition if we provide select interface as '*' but instead it enters when they are unequal. So I have already submitted a patch for that. And it is acknowledged. Change done is:
- if (strcmp(arg, "*"))
+ if (!strcmp(arg, "*"))
next prev parent reply other threads:[~2022-09-19 11:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220829074821.283063-1-arshdeep.kaur@intel.com>
2022-09-06 16:31 ` [PATCH] SCSY-192443 Fix DPDK-dumpcap for XRAN Library Pattan, Reshma
[not found] ` <20220907162659.260812-1-arshdeep.kaur@intel.com>
2022-09-12 8:54 ` [PATCH v2] dumpcap: add the mutiprocess fileprefix support Kaur, Arshdeep
2022-09-12 12:43 ` Arshdeep Kaur
2022-09-12 14:50 ` Stephen Hemminger
2022-09-12 19:03 ` [RFT] dumpcap: add file-prefix option Stephen Hemminger
2022-09-16 8:19 ` Kaur, Arshdeep
2022-09-16 12:51 ` Ben Magistro
2022-09-16 15:35 ` Stephen Hemminger
2022-09-19 11:19 ` Kaur, Arshdeep [this message]
2022-09-23 11:46 ` Kaur, Arshdeep
2022-10-17 5:08 ` Kaur, Arshdeep
2022-10-20 10:43 ` Kaur, Arshdeep
2022-10-20 15:40 ` Stephen Hemminger
2022-10-20 11:55 ` Kaur, Arshdeep
2022-10-21 13:07 ` David Marchand
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=DM6PR11MB3737B0B7C327638D5F493B55F04D9@DM6PR11MB3737.namprd11.prod.outlook.com \
--to=arshdeep.kaur@intel.com \
--cc=dev@dpdk.org \
--cc=koncept1@gmail.com \
--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).