DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/5] app/test-pmd: fix nb_rxq and np_txq checks
Date: Fri, 5 Feb 2016 08:48:59 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8A01EB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1454073052-27025-2-git-send-email-reshma.pattan@intel.com>

Hi Reshma,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Reshma Pattan
> Sent: Friday, January 29, 2016 1:11 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 1/5] app/test-pmd: fix nb_rxq and np_txq checks
> 
> Made testpmd changes to validate nb_rxq/nb_txq zero
> value changes of librte_ether.
> 
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> ---
>  app/test-pmd/cmdline.c    |   11 +++++------
>  app/test-pmd/parameters.c |   14 +++++++++-----
>  app/test-pmd/testpmd.c    |   19 +++++++++++++++++--
>  3 files changed, 31 insertions(+), 13 deletions(-)
> 
> diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c
> index 6d28c1b..fa666d2 100644
> --- a/app/test-pmd/cmdline.c
> +++ b/app/test-pmd/cmdline.c
> @@ -1,7 +1,7 @@
>  /*-
>   *   BSD LICENSE
>   *
> - *   Copyright(c) 2010-2015 Intel Corporation. All rights reserved.
> + *   Copyright(c) 2010-2016 Intel Corporation. All rights reserved.
>   *   Copyright(c) 2014 6WIND S.A.
>   *   All rights reserved.
>   *
> @@ -1163,17 +1163,16 @@ cmd_config_rx_tx_parsed(void *parsed_result,
>  		printf("Please stop all ports first\n");
>  		return;
>  	}
> -
>  	if (!strcmp(res->name, "rxq")) {
> -		if (res->value <= 0) {
> -			printf("rxq %d invalid - must be > 0\n", res->value);
> +		if (!res->value && !nb_txq) {
> +			printf("Warning: Either rx or tx queues should non be
> zero\n");

Typo: Either "should be non-zero" or "should not be zero". Same below.

>  			return;
>  		}
>  		nb_rxq = res->value;
>  	}
>  	else if (!strcmp(res->name, "txq")) {
> -		if (res->value <= 0) {
> -			printf("txq %d invalid - must be > 0\n", res->value);
> +		if (!res->value && !nb_rxq) {
> +			printf("Warning: Either rx or tx queues should non be
> zero\n");
>  			return;
>  		}
>  		nb_txq = res->value;

[...]

> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
> index 1319917..4c8afba 100644
> --- a/app/test-pmd/testpmd.c
> +++ b/app/test-pmd/testpmd.c
> @@ -1,7 +1,7 @@
>  /*-
>   *   BSD LICENSE
>   *
> - *   Copyright(c) 2010-2015 Intel Corporation. All rights reserved.
> + *   Copyright(c) 2010-2016 Intel Corporation. All rights reserved.
>   *   All rights reserved.
>   *
>   *   Redistribution and use in source and binary forms, with or without
> @@ -608,6 +608,7 @@ init_fwd_streams(void)
>  	portid_t pid;
>  	struct rte_port *port;
>  	streamid_t sm_id, nb_fwd_streams_new;
> +	queueid_t q;
> 
>  	/* set socket id according to numa or not */
>  	FOREACH_PORT(pid, ports) {
> @@ -643,7 +644,12 @@ init_fwd_streams(void)
>  		}
>  	}
> 
> -	nb_fwd_streams_new = (streamid_t)(nb_ports * nb_rxq);
> +	q = RTE_MAX(nb_rxq, nb_txq);
> +	if (q == 0) {
> +		printf("Fail:Cannot allocate fwd streams as number of
> queues is 0\n");
> +		return -1;
> +	}
> +	nb_fwd_streams_new = (streamid_t)(nb_ports * q);
>  	if (nb_fwd_streams_new == nb_fwd_streams)
>  		return 0;
>  	/* clear the old */
> @@ -955,6 +961,12 @@ start_packet_forwarding(int with_tx_first)
>  	portid_t   pt_id;
>  	streamid_t sm_id;
> 
> +	if (strcmp(cur_fwd_eng->fwd_mode_name, "rxonly") == 0 &&
> !nb_rxq)
> +		rte_exit(EXIT_FAILURE, "rxq are 0, cannot use rxonly fwd
> mode\n");
> +
> +	if (strcmp(cur_fwd_eng->fwd_mode_name, "txonly") == 0 &&
> !nb_txq)
> +		rte_exit(EXIT_FAILURE, "txq are 0, cannot use txonly fwd
> mode\n");
> +

Should we check if we have both rxq and txq > 0 when running
the other forwarding modes that need both RX/TX queues?

>  	if (all_ports_started() == 0) {
>  		printf("Not all ports were started\n");
>  		return;
> @@ -2037,6 +2049,9 @@ main(int argc, char** argv)
>  	if (argc > 1)
>  		launch_args_parse(argc, argv);
> 
> +	if (!nb_rxq && !nb_txq)
> +		printf("Warning: Either rx or tx queues should be non-
> zero\n");
> +
>  	if (nb_rxq > nb_txq)
>  		printf("Warning: nb_rxq=%d enables RSS configuration, "
>  		       "but nb_txq=%d will prevent to fully test it.\n",

Since we are allowing testpmd to run with nb_txq = 0, if nb_rxq = 1 and nb_txq = 0,
this warning above will be showed, because before if nb_rxq > nb_txq,
it would mean that nb_rxq is at least 2, so RSS is enabled, but now it might not be,
so this message has to be changed.

> --
> 1.7.4.1

  reply	other threads:[~2016-02-05  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 13:10 [dpdk-dev] [PATCH 0/5] add dpdk packet capture support for tcpdump Reshma Pattan
2016-01-29 13:10 ` [dpdk-dev] [PATCH 1/5] app/test-pmd: fix nb_rxq and np_txq checks Reshma Pattan
2016-02-05  8:48   ` De Lara Guarch, Pablo [this message]
2016-01-29 13:10 ` [dpdk-dev] [PATCH 2/5] drivers/net/pcap: add public api to create pcap device Reshma Pattan
2016-01-29 13:10 ` [dpdk-dev] [PATCH 3/5] app/proc_info: add tcpdump support in secondary process Reshma Pattan
2016-01-29 13:10 ` [dpdk-dev] [PATCH 4/5] lib/librte_eal: add tcpdump support in primary process Reshma Pattan
2016-01-29 13:10 ` [dpdk-dev] [PATCH 5/5] doc: update doc for tcpdump feature Reshma Pattan

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=E115CCD9D858EF4F90C690B0DCB4D8973C8A01EB@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=reshma.pattan@intel.com \
    /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).