From: Jeff Daly <jeffd@silicom-usa.com>
To: dev@dpdk.org
Cc: stable@dpdk.org
Subject: [PATCH 0/3] ixgbe: fix SFP hotplug detection
Date: Thu, 19 May 2022 15:25:12 -0400 [thread overview]
Message-ID: <cover.1652987887.git.jeffd@silicom-usa.com> (raw)
Currently the ixgbe driver does not ID any SFP except for the first one
plugged in. This can lead to no-link, or incorrect speed conditions.
For example:
* If link is initially established with a 1G SFP, and later a 1G/10G
multispeed part is later installed, then the MAC link setup functions are
never called to change from 1000BASE-X to 10GBASE-R mode, and the link
stays running at the slower rate.
* If link is initially established with a 1G SFP, and later a 10G only
module is later installed, no link is established, since we are still
trasnsmitting in 1000BASE-X mode to a 10GBASE-R only partner.
Refactor the SFP ID/setup, and link setup code, to more closely match the
flow of the mainline kernel driver which does not have these issues. In
that driver a service task runs periodically to handle these operations
based on bit flags that have been set (usually via interrupt or userspace
request), and then get cleared once the requested subtask has been
completed.
Fixes: af75078fece ("first public release")
Cc: stable@dpdk.org
Jeff Daly (3):
ixgbe: make link update thread periodic
ixgbe: move periodic link service work into separate function
ixgbe: make hotplug detection aware of changed SFPs
drivers/net/ixgbe/base/ixgbe_common.c | 4 +-
drivers/net/ixgbe/ixgbe_ethdev.c | 471 ++++++++++++++++++++------
drivers/net/ixgbe/ixgbe_ethdev.h | 9 +
3 files changed, 374 insertions(+), 110 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-19 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 19:25 Jeff Daly [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-19 18:02 [PATCH 0/3] ixgbe: Fix " Jeff Daly
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=cover.1652987887.git.jeffd@silicom-usa.com \
--to=jeffd@silicom-usa.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).