From: patchwork-bot+netdevbpf@kernel.org
To: Wang Zhan <wang.zhan@smartx.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
keyong.sun@smartx.com
Subject: Re: [PATCH net-next v2 0/2] net: sysfs: use ops lock for speed and duplex
Date: Tue, 08 Sep 2026 13:40:09 +0000 [thread overview]
Message-ID: <178887480914.3534869.13453609743422351581.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903133314.3703381-1-wang.zhan@smartx.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 3 Sep 2026 21:33:12 +0800 you wrote:
> Reading speed and duplex from sysfs currently holds RTNL across the
> get_link_ksettings callback. This unnecessarily serializes monitoring
> reads with unrelated rtnetlink operations.
>
> On CPU-throttled hosts, a periodic reader such as node-exporter can hold
> RTNL for hundreds of milliseconds while an mlx5 callback runs, delaying
> unrelated rtnetlink operations.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: sysfs: factor out link settings read
https://git.kernel.org/netdev/net-next/c/fc73b71c1bdb
- [net-next,v2,2/2] net: sysfs: use ops lock for speed and duplex
https://git.kernel.org/netdev/net-next/c/5d074ded6714
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-08 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 13:33 [PATCH net-next v2 0/2] net: sysfs: use ops lock for speed and duplex Wang Zhan
2026-09-03 13:33 ` [PATCH net-next v2 1/2] net: sysfs: factor out link settings read Wang Zhan
2026-09-03 13:33 ` [PATCH net-next v2 2/2] net: sysfs: use ops lock for speed and duplex Wang Zhan
2026-09-08 13:40 ` patchwork-bot+netdevbpf [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=178887480914.3534869.13453609743422351581.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=keyong.sun@smartx.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wang.zhan@smartx.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.