DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bernard Iremonger <bernard.iremonger@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] app/testpmd: fix log of start command
Date: Tue, 22 May 2018 11:35:40 +0100	[thread overview]
Message-ID: <1d5b66b2-5bc9-8b70-b25d-215ffc4699e6@intel.com> (raw)
In-Reply-To: <1526984578-11712-1-git-send-email-bernard.iremonger@intel.com>

On 5/22/2018 11:22 AM, Bernard Iremonger wrote:
> Call the rte_eth_rxq_info_get() and rte_eth_txq_info_get() functions
> to update the number of rx and tx descriptors.
> 
> Fixes: d44f8a485f5d ("app/testpmd: enable per queue configure")
> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> ---
>  app/test-pmd/config.c | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
> index 4520084..339651f 100644
> --- a/app/test-pmd/config.c
> +++ b/app/test-pmd/config.c
> @@ -1839,6 +1839,9 @@ struct igb_ring_desc_16_bytes {
>  		struct rte_eth_txconf *tx_conf = &ports[pid].tx_conf[0];
>  		uint16_t *nb_rx_desc = &ports[pid].nb_rx_desc[0];
>  		uint16_t *nb_tx_desc = &ports[pid].nb_tx_desc[0];
> +		struct rte_eth_rxq_info rx_qinfo;
> +		struct rte_eth_txq_info tx_qinfo;
> +		int32_t rc;
>  
>  		/* per port config */
>  		printf("  port %d: RX queue number: %d Tx queue number: %d\n",
> @@ -1850,6 +1853,10 @@ struct igb_ring_desc_16_bytes {
>  
>  		/* per rx queue config only for first queue to be less verbose */
>  		for (qid = 0; qid < 1; qid++) {
> +			rc = rte_eth_rx_queue_info_get(pid, qid, &rx_qinfo);
> +			if (!rc)
> +				nb_rx_desc[qid] = rx_qinfo.nb_desc;

Hi Bernard,

Isn't this doing same thing with previous patch, in a different location?

Do you think testpmd config variable should be updated?
Why not just use the value for print but not save it?

> +
>  			printf("    RX queue: %d\n", qid);
>  			printf("      RX desc=%d - RX free threshold=%d\n",
>  				nb_rx_desc[qid], rx_conf[qid].rx_free_thresh);
> @@ -1864,6 +1871,10 @@ struct igb_ring_desc_16_bytes {
>  
>  		/* per tx queue config only for first queue to be less verbose */
>  		for (qid = 0; qid < 1; qid++) {
> +			rc = rte_eth_tx_queue_info_get(pid, qid, &tx_qinfo);
> +			if (!rc)
> +				nb_tx_desc[qid] = tx_qinfo.nb_desc;
> +
>  			printf("    TX queue: %d\n", qid);
>  			printf("      TX desc=%d - TX free threshold=%d\n",
>  				nb_tx_desc[qid], tx_conf[qid].tx_free_thresh);
> 

  reply	other threads:[~2018-05-22 10:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 16:24 [dpdk-dev] [PATCH] app/test-pmd: fix testpmd " Bernard Iremonger
2018-05-18 11:52 ` Ferruh Yigit
2018-05-21 13:28 ` [dpdk-dev] [PATCH v2] app/testpmd: fix " Bernard Iremonger
2018-05-21 14:15   ` Ferruh Yigit
2018-05-22  9:06     ` Iremonger, Bernard
2018-05-22 10:22   ` [dpdk-dev] [PATCH v3] " Bernard Iremonger
2018-05-22 10:35     ` Ferruh Yigit [this message]
2018-05-22 10:46       ` Iremonger, Bernard
2018-05-22 15:10     ` [dpdk-dev] [PATCH v4] " Bernard Iremonger
2018-05-22 16:31       ` Ferruh Yigit
2018-05-22 16:42         ` Ferruh Yigit

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=1d5b66b2-5bc9-8b70-b25d-215ffc4699e6@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.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).