From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Martin Weiser <martin.weiser@allegro-packets.com>,
"rahul.lakkireddy@chelsio.com" <rahul.lakkireddy@chelsio.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] cxgbe: report 100G link speed capability for Chelsio T6 adapters
Date: Thu, 22 Jun 2017 09:35:19 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA640C30BE7@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1498121851-33487-1-git-send-email-martin.weiser@allegro-packets.com>
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Martin Weiser
> Sent: Thursday, June 22, 2017 9:58 AM
> To: rahul.lakkireddy@chelsio.com
> Cc: dev@dpdk.org; Martin Weiser <martin.weiser@allegro-packets.com>
> Subject: [dpdk-dev] [PATCH v2] cxgbe: report 100G link speed capability for Chelsio T6
> adapters
>
> These adapters support 100G link speed but the speed_capa bitmask in the
> device info did not reflect that.
>
> Signed-off-by: Martin Weiser <martin.weiser@allegro-packets.com>
> ---
> drivers/net/cxgbe/cxgbe_ethdev.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/cxgbe/cxgbe_ethdev.c b/drivers/net/cxgbe/cxgbe_ethdev.c
> index b622d25..b0d5ed7 100644
> --- a/drivers/net/cxgbe/cxgbe_ethdev.c
> +++ b/drivers/net/cxgbe/cxgbe_ethdev.c
> @@ -175,7 +175,11 @@ static void cxgbe_dev_info_get(struct rte_eth_dev *eth_dev,
>
> device_info->rx_desc_lim = cxgbe_desc_lim;
> device_info->tx_desc_lim = cxgbe_desc_lim;
> - device_info->speed_capa = ETH_LINK_SPEED_10G | ETH_LINK_SPEED_40G;
> + if (CHELSIO_CHIP_VERSION(adapter->params.chip) == CHELSIO_T6)
> + device_info->speed_capa = ETH_LINK_SPEED_10G | ETH_LINK_SPEED_40G |
> + ETH_LINK_SPEED_100G;
> + else
> + device_info->speed_capa = ETH_LINK_SPEED_10G | ETH_LINK_SPEED_40G;
> }
I think the following code is simpler and shows intent clearer?
No objection to the patch above from me, just a suggestion :)
device_info->speed_capa = ETH_LINK_SPEED_10G | ETH_LINK_SPEED_40G;
if (CHELSIO_CHIP_VERSION(adapter->params.chip) == CHELSIO_T6)
device_info->speed_capa |= ETH_LINK_SPEED_100G;
next prev parent reply other threads:[~2017-06-22 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 8:57 Martin Weiser
2017-06-22 9:35 ` Van Haaren, Harry [this message]
2017-06-22 9:59 ` Martin Weiser
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=E923DB57A917B54B9182A2E928D00FA640C30BE7@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=martin.weiser@allegro-packets.com \
--cc=rahul.lakkireddy@chelsio.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).