From: Marc <marcdevel@gmail.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] e1000: randomly loosing link change events triggered by the peer
Date: Mon, 28 Mar 2016 13:02:57 +0200 [thread overview]
Message-ID: <CAExC=0RFfX-mMfa9_p1dd5t4_jZhtD7v-vk8Rz6_HneoGH9qqw@mail.gmail.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09090343F665@shsmsx102.ccr.corp.intel.com>
On 28 March 2016 at 03:54, Lu, Wenzhuo <wenzhuo.lu@intel.com> wrote:
> Hi Marc
>
>
>
> *From:* Marc Sune [mailto:marcdevel@gmail.com]
> *Sent:* Saturday, March 26, 2016 9:43 AM
> *To:* dev@dpdk.org; Lu, Wenzhuo
> *Subject:* e1000: randomly loosing link change events triggered by the
> peer
>
>
>
> I found that in the current HEAD in master testing it with an I218-LM in
> autoneg mode, when link is forced to be renegociated by the peer (e.g. via
> ethtool on a peer Linux box) _some_ change events are lost.
>
>
>
> It is quite random, but it seems to happen more while changing the speed
> than when changing the duplex mode.
>
>
>
> However, when one or more link change events have been lost and the phy
> medium is disconnected and reconnected, the link speed and duplex mode are
> then correctly updated.
>
>
>
> Marc
>
>
>
> [Wenzhuo] Thanks for let us know this issue. May I ask some questions? Do
> you mean this NIC 0x155A?
>
0x15A2, I218-LM (rev 03)
EAL: PCI device 0000:00:19.0 on NUMA socket -1
EAL: probe driver: 8086:15a2 rte_em_pmd
EAL: PCI memory mapped at 0x7f85cf400000
EAL: PCI memory mapped at 0x7f85cf420000
PMD: eth_em_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x15a2
I think this is not a NIC issue, but a general problem of the driver (or em
code).
> About how to reproduce this problem, you mean use these CLIs, ethtool –s
> xxx advertise xxx, ethtool –s xxx duplex half/full, to change the peer
> port’s configuration?
>
Correct. I modified l2fwd to check link status and print it on each port
stats print iteration. Then from the peer I modified the link properties
via ethtool.
The result is that transitions from autoneg speeds and/or duplex mode
settings are randomly not detected (rte_eth_link in rte_eth_dev_data is not
updated), and it prints not-up-to-date state.
Marc
next prev parent reply other threads:[~2016-03-28 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 1:42 Marc Sune
2016-03-28 1:54 ` Lu, Wenzhuo
2016-03-28 11:02 ` Marc [this message]
2016-03-29 1:19 ` Lu, Wenzhuo
2016-03-30 8:04 ` Marc
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='CAExC=0RFfX-mMfa9_p1dd5t4_jZhtD7v-vk8Rz6_HneoGH9qqw@mail.gmail.com' \
--to=marcdevel@gmail.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@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).