From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Herakliusz Lipiec <herakliusz.lipiec@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>
Cc: dev@dpdk.org, qimaix.xiao@intel.com, ying.a.wang@intel.com
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add warning message when user sets rxq greater than txq
Date: Thu, 27 Jun 2019 16:25:42 +0100 [thread overview]
Message-ID: <965a59f8-f08e-958f-24ea-1080a95d8765@intel.com> (raw)
In-Reply-To: <20190502154446.35861-1-herakliusz.lipiec@intel.com>
On 5/2/2019 4:44 PM, Herakliusz Lipiec wrote:
> add a warning message when user sets port config all rxq value larger
> than txq in interactive mode.
>
> Signed-off-by: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Hi Hero,
Can you please give some context that why we need this check? What is broken
without this check?
Thanks,
ferruh
> ---
> app/test-pmd/cmdline.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c
> index 5a10c5f38..94be3c6f8 100644
> --- a/app/test-pmd/cmdline.c
> +++ b/app/test-pmd/cmdline.c
> @@ -1741,6 +1741,10 @@ cmd_config_rx_tx_parsed(void *parsed_result,
> }
> if (check_nb_rxq(res->value) != 0)
> return;
> + if (res->value > nb_txq) {
> + printf("Warning: rxq should not be larger than txq\n");
> + return;
> + }
> nb_rxq = res->value;
> }
> else if (!strcmp(res->name, "txq")) {
> @@ -1750,6 +1754,10 @@ cmd_config_rx_tx_parsed(void *parsed_result,
> }
> if (check_nb_txq(res->value) != 0)
> return;
> + if (res->value < nb_rxq) {
> + printf("Warning: rxq should not be larger than txq\n");
> + return;
> + }
> nb_txq = res->value;
> }
> else if (!strcmp(res->name, "rxd")) {
>
prev parent reply other threads:[~2019-06-27 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 15:44 Herakliusz Lipiec
2019-05-02 15:44 ` Herakliusz Lipiec
2019-06-07 13:25 ` Iremonger, Bernard
2019-06-27 15:25 ` Ferruh Yigit [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=965a59f8-f08e-958f-24ea-1080a95d8765@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=herakliusz.lipiec@intel.com \
--cc=jingjing.wu@intel.com \
--cc=qimaix.xiao@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=ying.a.wang@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).