From: "Zhang, Helin" <helin.zhang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 7/7] app/testpmd: rework for displaying different size of RX descriptors
Date: Mon, 23 Jun 2014 01:38:07 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A745C43@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <45267557.BLbedC010Y@xps13>
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Friday, June 20, 2014 10:35 PM
To: Zhang, Helin
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 7/7] app/testpmd: rework for displaying different size of RX descriptors
2014-06-20 14:14, Helin Zhang:
> i40e supports 16 and 32 bytes RX descriptors which can be configured.
> It needs to check the driver type and the configuration to determine
> if 16 or 32 bytes RX descriptors is being used, for reading and
> displaying the different sizes of RX descriptors.
[...]
> + if (strstr(dev_info.driver_name, "i40e") != NULL) { /* i40e */
> +#ifndef RTE_LIBRTE_I40E_16BYTE_RX_DESC
Do we need to handle i40e case if RTE_LIBRTE_I40E_16BYTE_RX_DESC is defined?
[simplified diff follows]
> #else
> + struct igb_ring_desc_16_bytes *ring =
> + (struct igb_ring_desc_16_bytes *)ring_mz->addr;
>
> + ring_rxd_display_dword(rte_le_to_cpu_64(\
> + ring[desc_id].lo_dword));
> + ring_rxd_display_dword(rte_le_to_cpu_64(\
> + ring[desc_id].hi_dword));
> #endif
> + } else { /* not i40e */
> + struct igb_ring_desc_16_bytes *ring =
> + (struct igb_ring_desc_16_bytes *)ring_mz->addr;
> +
> + ring_rxd_display_dword(rte_le_to_cpu_64(\
> + ring[desc_id].lo_dword));
> + ring_rxd_display_dword(rte_le_to_cpu_64(\
> + ring[desc_id].hi_dword));
> + }
You could factorize these 2 cases.
--
Thomas
----------------------------------------------------------------------------------------------------------------
Hi Thomas
As RX descriptor size can vary in i40e only, and for other PMD, RTE_LIBRTE_I40E_16BYTE_RX_DESC will never be defined, we need to handle all possibilities.
Yes, I can rework the changes and let it be more graceful. Thanks!
Regards,
Helin
next prev parent reply other threads:[~2014-06-23 1:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 6:14 [dpdk-dev] [PATCH 0/7] enhancements for i40e Helin Zhang
2014-06-20 6:14 ` [dpdk-dev] [PATCH 1/7] i40e: fix for getting correct RSS hash result Helin Zhang
2014-06-20 6:14 ` [dpdk-dev] [PATCH 2/7] i40evf: support configuring crc stripping hw offload Helin Zhang
2014-06-20 14:08 ` Thomas Monjalon
2014-06-23 2:29 ` Zhang, Helin
2014-06-20 6:14 ` [dpdk-dev] [PATCH 3/7] i40e: ignore the failure of updating default filter settings Helin Zhang
2014-06-20 14:16 ` Thomas Monjalon
2014-06-23 2:21 ` Zhang, Helin
2014-06-20 6:14 ` [dpdk-dev] [PATCH 4/7] i40e: fix for updating the hash lookup table of PF RSS Helin Zhang
2014-06-20 6:14 ` [dpdk-dev] [PATCH 5/7] i40e: double vlan should be specifically disabled by default Helin Zhang
2014-06-20 6:14 ` [dpdk-dev] [PATCH 6/7] i40evf: fix for copying wrong size of link info, and remove an useless function Helin Zhang
2014-06-20 14:28 ` Thomas Monjalon
2014-06-20 6:14 ` [dpdk-dev] [PATCH 7/7] app/testpmd: rework for displaying different size of RX descriptors Helin Zhang
2014-06-20 14:34 ` Thomas Monjalon
2014-06-23 1:38 ` Zhang, Helin [this message]
2014-06-20 6:23 ` [dpdk-dev] [PATCH 0/7] enhancements for i40e Zhang, Helin
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A745C43@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).