From: Laurent Hardy <laurent.hardy@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
"Dai, Wei" <wei.dai@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ixgbe: ensure link status is updated
Date: Tue, 11 Apr 2017 14:13:17 +0200 [thread overview]
Message-ID: <58ECC85D.4010403@6wind.com> (raw)
In-Reply-To: <8ce85605-3e52-6088-754e-29ee892681c6@intel.com>
On 04/10/2017 03:36 PM, Ferruh Yigit wrote:
> On 4/3/2017 2:23 PM, Laurent Hardy wrote:
>> Hi Wei,
>> Thanks for your reply.
>>
>> If autoneg is false, then we set a default speed to the highest value
>> before performing the link setup.
>> You are right, there is no relevant reason to keep this check on speed
>> mask> should be:
>> + if (!autoneg)
>> + speed = IXGBE_LINK_SPEED_10GB_FULL;
> Hi Laurent,
>
> Should we expect a new version of the patch with above update?
Hi Ferruh,
yes, I will send a new version today.
regards,
Laurent
> Thanks,
> ferruh
>
>> Patch has been tested using testpmd with following setups:
>>
>> Autoneg setup:
>> =========
>> - On dut, both ports of 82599 are connected to a switch with 1Gb ports
>> - auto-negotiate option is enabled on switch
>>
>> Defined speed setup:
>> ============
>> - set link speed to 1Gb on both ports of the switch connected to the dut
>>
> <...>
>
>>
>> Thanks & regards,
>> Laurent
>>
>> On 03/30/2017 06:32 PM, Dai, Wei wrote:
>>> Hi, Olivier
>>>
>>> Has anyone already tested this patch ?
>>> Can you present some useful info on how to test it ?
>>> Can I use ethtool with some argument to downgrade or upgrade the rate of peer port ?
>>>
>>> I have just run testpmd with 82599, the hw->phy. autoneg_advertised is 0 after rte_eal_init() and rte_eth_dev_start().
>>> So I think the codes in if (!speed) { ... } is likely to be run.
>>> I agree with most of your codes.
>>> But why to limit speed of NIC to 10Gbps if autoneg is false and 10Gbps is supported ?
>>> In this case, how about setting multiple speed ?
>>>
>>> Thanks
>>> -Wei
>>>
>>>
> <...>
>
>
next prev parent reply other threads:[~2017-04-11 12:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 17:29 [dpdk-dev] [PATCH] " Laurent Hardy
2016-11-28 17:27 ` Laurent Hardy
2016-12-08 17:10 ` Ferruh Yigit
2017-02-01 14:14 ` Thomas Monjalon
2017-02-08 15:51 ` Dai, Wei
2017-02-08 17:03 ` Olivier MATZ
2017-02-13 3:17 ` Dai, Wei
2017-02-16 16:32 ` [dpdk-dev] [PATCH v2] " Olivier Matz
2017-03-30 9:19 ` Olivier Matz
2017-03-30 16:32 ` Dai, Wei
2017-04-03 13:23 ` Laurent Hardy
2017-04-10 13:36 ` Ferruh Yigit
2017-04-11 12:13 ` Laurent Hardy [this message]
2017-04-12 8:21 ` [dpdk-dev] [PATCH] " Laurent Hardy
2017-04-18 14:33 ` Dai, Wei
2017-04-27 15:03 ` [dpdk-dev] [PATCH v4] " Laurent Hardy
2017-04-28 0:43 ` Dai, Wei
2017-04-28 5:23 ` Ferruh Yigit
2017-05-17 13:31 ` Roger B Melton
2017-05-22 18:54 ` [dpdk-dev] 2nd try: problem with ixgbe_dev_link_update() for multi-speed fiber [was] " Roger B. Melton
2017-05-23 7:24 ` Dai, Wei
2017-05-23 7:41 ` Dai, Wei
2017-05-24 14:40 ` Roger B. Melton
2017-05-24 18:38 ` Roger B. Melton
2017-06-02 16:15 ` Roger B. Melton
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=58ECC85D.4010403@6wind.com \
--to=laurent.hardy@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.com \
--cc=wei.dai@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).