All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhuyj <zyjzyj2000@gmail.com>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>,
	"Schmitt, Phillip J" <phillip.j.schmitt@intel.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>,
	"Shteinbock, Boris (Wind River)" <boris.shteinbock@windriver.com>
Subject: Re: ixgbe: get link speed as a slave nic unrelated with link
Date: Wed, 3 Feb 2016 18:17:48 +0800	[thread overview]
Message-ID: <56B1D3CC.4050202@gmail.com> (raw)
In-Reply-To: <87618083B2453E4A8714035B62D67992505210DB@FMSMSX105.amr.corp.intel.com>

Hi, Emil

Thanks for your reply.

I made simple tests. And maybe this patch should work. Because you can
reproduce this problem, would you like to make tests with this patch?

If this patch can fix this problem, it can prove that the root cause is 
correct.
We can find another solution to fix this problem.

If this patch can not fix this problem, maybe we should make further 
investigations
to find the root cause.

Thanks a lot.
Zhu Yanjun

On 02/01/2016 11:53 PM, Tantilov, Emil S wrote:
>> -----Original Message-----
>> From: zyjzyj2000@gmail.com [mailto:zyjzyj2000@gmail.com]
>> Sent: Sunday, January 31, 2016 11:28 PM
>> To: zyjzyj2000@gmail.com; Tantilov, Emil S; Schmitt, Phillip J; Kirsher,
>> Jeffrey T; netdev@vger.kernel.org; e1000-devel@lists.sourceforge.net;
>> Shteinbock, Boris (Wind River)
>> Subject: ixgbe: get link speed as a slave nic unrelated with link
>>
>>
>> Hi, Emil
>>
>> Thanks for your patch.
>> After I applied your patch, the following are the feedback from my users.
>>
>> "
>> Users had tested the latest patch that you provided and it is much improved
>> now. However it’s still not good enough as the users are planning field
>> deployment. Here are their findings:
>>
>> So close, but not quite 100%. I did run over 2500 re-negotiations on one
>> interface of a bonded pair and got the 0 MBps status total of three times.
>> The longest run without single error was something like 1800 re-
>> negotiations or so. So, this version seems to improve the situation
>> immensely (the unpatched driver fails like 25% of the time), but there
>> still seems to remain some tiny race somewhere.
> Yes at the time of the bonding interface coming up there can be a message about 0 Mbps in dmesg,
> however the actual bond once fully up will have the correct speeds as seen by:
> #cat /proc/net/bonding/bond0
>
> Thanks,
> Emil
>
>

  reply	other threads:[~2016-02-03 10:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 13:00 [net-next 0/8][pull request] 10GbE Intel Wired LAN Driver Updates 2016-01-08 Jeff Kirsher
2016-01-08 13:00 ` [net-next 1/8] ixgbe: Fill at least min credits to a TC credit refills Jeff Kirsher
2016-01-08 13:00 ` [net-next 2/8] ixgbe: use correct FCoE DDP max check Jeff Kirsher
2016-01-08 13:00 ` [net-next 3/8] ixgbe: fix broken PFC with X550 Jeff Kirsher
2016-01-08 13:00 ` [net-next 4/8] ixgbe: do not call check_link for ethtool in ixgbe_get_settings() Jeff Kirsher
2016-02-01  7:27   ` ixgbe: get link speed as a slave nic unrelated with link zyjzyj2000
2016-02-01  7:27     ` [PATCH 1/1] ixgbe: get link speed as a slave nic unrelated with link up zyjzyj2000
2016-02-01 15:55       ` Tantilov, Emil S
2016-02-01 15:53     ` ixgbe: get link speed as a slave nic unrelated with link Tantilov, Emil S
2016-02-03 10:17       ` zhuyj [this message]
2016-01-08 13:00 ` [net-next 5/8] ixgbe: Correct handling of any outer UDP checksum setting Jeff Kirsher
2016-01-08 13:00 ` [net-next 6/8] ixgbe: Fix to get FDMI HBA attributes information with X550 Jeff Kirsher
2016-01-08 13:00 ` [net-next 7/8] ixgbe: Fix MDD events generated when FCoE+SRIOV are enabled Jeff Kirsher
2016-01-08 13:00 ` [net-next 8/8] ixgbe: Make ATR recognize IPv6 extended headers Jeff Kirsher
2016-01-08 18:49 ` [net-next 0/8][pull request] 10GbE Intel Wired LAN Driver Updates 2016-01-08 David Miller

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=56B1D3CC.4050202@gmail.com \
    --to=zyjzyj2000@gmail.com \
    --cc=boris.shteinbock@windriver.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=emil.s.tantilov@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=phillip.j.schmitt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.