From: patchwork-bot+netdevbpf@kernel.org
To: Qingfang Deng <qingfang.deng@linux.dev>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
ericwouds@gmail.com, manizada@pm.me, nbd@nbd.name,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] pppoe: use sk_node for session hash chains
Date: Thu, 12 Nov 2026 01:00:07 +0000 [thread overview]
Message-ID: <179444520767.1739789.10681932147394019452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110091255.24158-1-qingfang.deng@linux.dev>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Nov 2026 17:12:52 +0800 you wrote:
> PPPoE uses a private next pointer to chain sockets in each hash bucket.
> Removing a socket requires walking the chain to find its predecessor.
>
> Use sock.sk_node and the standard hlist helpers to allow constant-time
> removal and eliminate pppox_sock.next. Cache the bucket index in sk_hash
> before publishing the socket and use it to advance /proc/net/pppoe
> iteration between buckets.
>
> [...]
Here is the summary with links:
- [net-next] pppoe: use sk_node for session hash chains
https://git.kernel.org/netdev/net-next/c/7845123d30f9
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-11-12 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 9:12 [PATCH net-next] pppoe: use sk_node for session hash chains Qingfang Deng
2026-11-12 1:00 ` 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=179444520767.1739789.10681932147394019452.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=ericwouds@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manizada@pm.me \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@linux.dev \
/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.