DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Shrey Khandelwal <s.khandelwal@f5.com>
Cc: weh@microsoft.com, longli@microsoft.com, dev@dpdk.org
Subject: Re: [PATCH 0/2] net/netvsc: fix stale link status and speed
Date: Wed, 14 Oct 2026 10:33:13 -0700	[thread overview]
Message-ID: <20261014103313.76c1bfb6@phoenix.local> (raw)
In-Reply-To: <20261014020744.13605-1-s.khandelwal@f5.com>

On Tue, 13 Oct 2026 19:07:42 -0700
Shrey Khandelwal <s.khandelwal@f5.com> wrote:

> With LSC enabled, the link status and speed seen by the application
> are not updated after the host reports a link change.
> 
> Patch 1 makes sure the cached link always has the current speed.
> Patch 2 updates the cached link from the host indication.
> 
> Tested on Azure with testpmd, by injecting media disconnect, media
> connect and link speed change indications. Without the patches, the
> link read in the LSC callback stays up at the old speed. With them,
> it goes down, up, then shows the new speed.
> 
> Shrey Khandelwal (2):
>   net/netvsc: fix link speed not updated
>   net/netvsc: fix link status not updated on host indication
> 
>  .mailmap                       |  1 +
>  drivers/net/netvsc/hn_ethdev.c |  8 ++-
>  drivers/net/netvsc/hn_rndis.c  | 90 ++++++++++++++++++++++++++++++++--
>  drivers/net/netvsc/hn_rndis.h  |  3 +-
>  drivers/net/netvsc/hn_rxtx.c   |  2 +-
>  drivers/net/netvsc/hn_var.h    |  4 ++
>  6 files changed, 97 insertions(+), 11 deletions(-)
> 

Looks correct and review was clean. applied to next-net

      parent reply	other threads:[~2026-10-14 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  2:07 [PATCH 0/2] net/netvsc: fix stale link status and speed Shrey Khandelwal
2026-10-14  2:07 ` [PATCH 1/2] net/netvsc: fix link speed not updated Shrey Khandelwal
2026-10-14  2:07 ` [PATCH 2/2] net/netvsc: fix link status not updated on host indication Shrey Khandelwal
2026-10-14 17:33 ` Stephen Hemminger [this message]

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=20261014103313.76c1bfb6@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=longli@microsoft.com \
    --cc=s.khandelwal@f5.com \
    --cc=weh@microsoft.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