From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Daly, Jeff" <jeffd@silicom-usa.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Wu, Wenjun1" <wenjun1.wu@intel.com>
Cc: Stephen Douthit <stephend@silicom-usa.com>
Subject: RE: [PATCH 1/3] ixgbe: make link update thread periodic
Date: Sun, 29 May 2022 23:25:24 +0000 [thread overview]
Message-ID: <DM4PR11MB5994EB1DC7D6BBACCF6AFA83D7DA9@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220519180248.23831-2-jeffd@silicom-usa.com>
> -----Original Message-----
> From: Jeff Daly <jeffd@silicom-usa.com>
> Sent: Friday, May 20, 2022 2:03 AM
> To: dev@dpdk.org; Yang, Qiming <qiming.yang@intel.com>; Wu, Wenjun1
> <wenjun1.wu@intel.com>
> Cc: Stephen Douthit <stephend@silicom-usa.com>
> Subject: [PATCH 1/3] ixgbe: make link update thread periodic
>
> Rather than run-to-completion, allow the link update thread to be periodic.
> This will set the stage for properly handling hot-plugging.
Could you explain more about what's the hot-plugging issue with run-to-completion you try to fix?
>
> Signed-off-by: Jeff Daly <jeffd@silicom-usa.com>
> Inspired-by: Stephen Douthit <stephend@silicom-usa.com>
> ---
> drivers/net/ixgbe/base/ixgbe_common.c | 4 +-
> drivers/net/ixgbe/ixgbe_ethdev.c | 180 ++++++++++----------------
> 2 files changed, 71 insertions(+), 113 deletions(-)
>
> diff --git a/drivers/net/ixgbe/base/ixgbe_common.c
> b/drivers/net/ixgbe/base/ixgbe_common.c
> index aa843bd5c4a5..712062306491 100644
> --- a/drivers/net/ixgbe/base/ixgbe_common.c
> +++ b/drivers/net/ixgbe/base/ixgbe_common.c
> @@ -4154,8 +4154,8 @@ s32 ixgbe_check_mac_link_generic(struct
> ixgbe_hw *hw, ixgbe_link_speed *speed,
> break;
> case ixgbe_mac_X550EM_x:
> case ixgbe_mac_X550EM_a:
> - sfp_cage_full = IXGBE_READ_REG(hw, IXGBE_ESDP)
> &
> - IXGBE_ESDP_SDP0;
> + sfp_cage_full = !(IXGBE_READ_REG(hw, IXGBE_ESDP)
> &
> + IXGBE_ESDP_SDP0);
> break;
> default:
> /* sanity check - No SFP+ devices here */ diff --git
Looks like you change the behavior of link status check for x550.
I'm not an ixgbe expert, but I know this is not kernel driver's implementation.
So do you think this is a fix for both DPDK and kernel driver? if it is, please move this change into a separate patch and we need to reach the right expert to approve this.
next prev parent reply other threads:[~2022-05-29 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 18:02 [PATCH 0/3] ixgbe: Fix SFP hotplug detection Jeff Daly
2022-05-19 18:02 ` [PATCH 1/3] ixgbe: make link update thread periodic Jeff Daly
2022-05-29 23:25 ` Zhang, Qi Z [this message]
2022-05-30 13:46 ` Jeff Daly
2022-05-30 14:21 ` Zhang, Qi Z
2022-05-30 14:38 ` Zhang, Qi Z
2022-05-31 12:25 ` Jeff Daly
2022-05-31 13:03 ` Zhang, Qi Z
2022-05-19 18:02 ` [PATCH 2/3] ixgbe: move periodic link service work into separate function Jeff Daly
2022-05-19 18:02 ` [PATCH 3/3] ixgbe: make hotplug detection aware of changed SFPs Jeff Daly
-- strict thread matches above, loose matches on Subject: below --
2022-05-19 19:25 [PATCH 0/3] ixgbe: fix SFP hotplug detection Jeff Daly
2022-05-19 19:25 ` [PATCH 1/3] ixgbe: make link update thread periodic Jeff Daly
2022-05-19 17:43 [PATCH 0/3] ixgbe: Fix SFP hotplug detection/removal Jeff Daly
2022-05-19 17:43 ` [PATCH 1/3] ixgbe: make link update thread periodic 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=DM4PR11MB5994EB1DC7D6BBACCF6AFA83D7DA9@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jeffd@silicom-usa.com \
--cc=qiming.yang@intel.com \
--cc=stephend@silicom-usa.com \
--cc=wenjun1.wu@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).