DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kaur, Arshdeep" <arshdeep.kaur@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "koncept1@gmail.com" <koncept1@gmail.com>,
	"Pattan, Reshma" <reshma.pattan@intel.com>,
	"Chintalapalle, Balaji" <balaji.chintalapalle@intel.com>,
	"Beadle, Michael" <michael.beadle@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] dumpcap: fix list interfaces
Date: Tue, 4 Oct 2022 15:25:12 +0000	[thread overview]
Message-ID: <DM6PR11MB373738C2682DF21415F2DD6AF05A9@DM6PR11MB3737.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220925233410.98051-1-stephen@networkplumber.org>

Hi Stephen,

I tested the patch. "-D" option is now working properly.

But I am facing an issue in this.

Using "-D" provides me with the interfaces available. For me these are "0000:18:01.0" and "0000:18:09.0":
./dpdk-dumpcap -D --file-prefix wls_1
FlexRAN SDK bblib_lte_ldpc_decoder version #DIRTY#
FlexRAN SDK bblib_lte_ldpc_encoder version #DIRTY#
FlexRAN SDK bblib_lte_LDPC_ratematch version #DIRTY#
FlexRAN SDK bblib_lte_rate_dematching_5gnr version #DIRTY#
FlexRAN SDK bblib_lte_turbo version #DIRTY#
FlexRAN SDK bblib_lte_crc version #DIRTY#
FlexRAN SDK bblib_lte_rate_matching version #DIRTY#
FlexRAN SDK bblib_common version #DIRTY#
FlexRAN SDK bblib_srs_fft_cestimate_5gnr version #DIRTY#
FlexRAN SDK bblib_mldts_process_5gnr version #DIRTY#
EAL: 0000:18:01.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:18:01.1 cannot be used
EAL: 0000:18:09.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:18:09.1 cannot be used
EAL: 0000:18:11.0 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:18:11.0 cannot be used
EAL: 0000:18:11.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:18:11.1 cannot be used
EAL: 0000:18:19.0 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:18:19.0 cannot be used
EAL: 0000:18:19.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:18:19.1 cannot be used
EAL: 0000:af:01.0 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:af:01.0 cannot be used
EAL: 0000:af:01.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:af:01.1 cannot be used
EAL: 0000:af:09.0 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:af:09.0 cannot be used
EAL: 0000:af:09.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:af:09.1 cannot be used
EAL: 0000:af:11.0 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:af:11.0 cannot be used
EAL: 0000:af:11.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:af:11.1 cannot be used
EAL: 0000:af:19.0 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:af:19.0 cannot be used
EAL: 0000:af:19.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:af:19.1 cannot be used
0. 0000:18:01.0
1. 0000:18:09.0

But when I use these same interfaces to capture, they are not available:
./dpdk-dumpcap -i 0000:18:01.0 -c 500 -s 9600 -w capture1.pacp --file-prefix wls_1
FlexRAN SDK bblib_lte_ldpc_decoder version #DIRTY#
FlexRAN SDK bblib_lte_ldpc_encoder version #DIRTY#
FlexRAN SDK bblib_lte_LDPC_ratematch version #DIRTY#
FlexRAN SDK bblib_lte_rate_dematching_5gnr version #DIRTY#
FlexRAN SDK bblib_lte_turbo version #DIRTY#
FlexRAN SDK bblib_lte_crc version #DIRTY#
FlexRAN SDK bblib_lte_rate_matching version #DIRTY#
FlexRAN SDK bblib_common version #DIRTY#
FlexRAN SDK bblib_srs_fft_cestimate_5gnr version #DIRTY#
FlexRAN SDK bblib_mldts_process_5gnr version #DIRTY#
EAL: Error - exiting with code: 1
  Cause: Specified port_number "0000:18:01.0" is not a valid number

./dpdk-dumpcap -i 0000:18:09.0 -c 500 -s 9600 -w capture2.pacp --file-prefix wls_1
FlexRAN SDK bblib_lte_ldpc_decoder version #DIRTY#
FlexRAN SDK bblib_lte_ldpc_encoder version #DIRTY#
FlexRAN SDK bblib_lte_LDPC_ratematch version #DIRTY#
FlexRAN SDK bblib_lte_rate_dematching_5gnr version #DIRTY#
FlexRAN SDK bblib_lte_turbo version #DIRTY#
FlexRAN SDK bblib_lte_crc version #DIRTY#
FlexRAN SDK bblib_lte_rate_matching version #DIRTY#
FlexRAN SDK bblib_common version #DIRTY#
FlexRAN SDK bblib_srs_fft_cestimate_5gnr version #DIRTY#
FlexRAN SDK bblib_mldts_process_5gnr version #DIRTY#
EAL: Error - exiting with code: 1
  Cause: Specified port_number "0000:18:09.0" is not a valid number

According to me, select_interface() has same issue that dump_interfaces() had. So we need to add a flag for this in similar way and handle select_interface() in main after parse_opts, dpdk_init and dump_interfaces.

I tested this changes and it works for me. But I am not sure how it will affect entire dumpcap. Please let me know your thoughts about it.

Thanks and regards,
Arshdeep Kaur

> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Monday, September 26, 2022 5:04 AM
> To: dev@dpdk.org
> Cc: Stephen Hemminger <stephen@networkplumber.org>;
> koncept1@gmail.com; Pattan, Reshma <reshma.pattan@intel.com>
> Subject: [PATCH] dumpcap: fix list interfaces
> 
> The change to do argument process before EAL init broke the support of
> list-interfaces option. Fix by setting flag and doing list-interfaces later.
> 
> Fixes: a8dde09f97df ("app/dumpcap: allow help/version without primary
> process")
> Cc: koncept1@gmail.com
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  app/dumpcap/main.c | 19 +++++++++++++------
>  1 file changed, 13 insertions(+), 6 deletions(-)
> 
> diff --git a/app/dumpcap/main.c b/app/dumpcap/main.c index
> a6041d4ff495..490a0f050bc8 100644
> --- a/app/dumpcap/main.c
> +++ b/app/dumpcap/main.c
> @@ -63,6 +63,8 @@ static unsigned int ring_size = 2048;  static const char
> *capture_comment;  static uint32_t snaplen =
> RTE_MBUF_DEFAULT_BUF_SIZE;  static bool dump_bpf;
> +static bool show_interfaces;
> +
>  static struct {
>  	uint64_t  duration;	/* nanoseconds */
>  	unsigned long packets;  /* number of packets in file */ @@ -256,7
> +258,7 @@ static void select_interface(const char *arg)  }
> 
>  /* Display list of possible interfaces that can be used. */ -static void
> show_interfaces(void)
> +static void dump_interfaces(void)
>  {
>  	char name[RTE_ETH_NAME_MAX_LEN];
>  	uint16_t p;
> @@ -266,6 +268,8 @@ static void show_interfaces(void)
>  			continue;
>  		printf("%u. %s\n", p, name);
>  	}
> +
> +	exit(0);
>  }
> 
>  static void compile_filter(void)
> @@ -353,8 +357,8 @@ static void parse_opts(int argc, char **argv)
>  			dump_bpf = true;
>  			break;
>  		case 'D':
> -			show_interfaces();
> -			exit(0);
> +			show_interfaces = true;
> +			break;
>  		case 'f':
>  			filter_str = optarg;
>  			break;
> @@ -529,9 +533,6 @@ static void dpdk_init(void)
> 
>  	if (rte_eal_init(eal_argc, eal_argv) < 0)
>  		rte_exit(EXIT_FAILURE, "EAL init failed: is primary process
> running?\n");
> -
> -	if (rte_eth_dev_count_avail() == 0)
> -		rte_exit(EXIT_FAILURE, "No Ethernet ports found\n");
>  }
> 
>  /* Create packet ring shared between callbacks and process */ @@ -789,6
> +790,12 @@ int main(int argc, char **argv)
>  	parse_opts(argc, argv);
>  	dpdk_init();
> 
> +	if (show_interfaces)
> +		dump_interfaces();
> +
> +	if (rte_eth_dev_count_avail() == 0)
> +		rte_exit(EXIT_FAILURE, "No Ethernet ports found\n");
> +
>  	if (filter_str)
>  		compile_filter();
> 
> --
> 2.35.1


      parent reply	other threads:[~2022-10-04 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 23:34 Stephen Hemminger
2022-09-29 13:22 ` Pattan, Reshma
2022-10-10  0:04   ` Thomas Monjalon
2022-10-04 15:25 ` Kaur, Arshdeep [this message]

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=DM6PR11MB373738C2682DF21415F2DD6AF05A9@DM6PR11MB3737.namprd11.prod.outlook.com \
    --to=arshdeep.kaur@intel.com \
    --cc=balaji.chintalapalle@intel.com \
    --cc=dev@dpdk.org \
    --cc=koncept1@gmail.com \
    --cc=michael.beadle@intel.com \
    --cc=reshma.pattan@intel.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).