From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH v3 net-next 0/7] rfs: use high-order allocations for hash tables
Date: Thu, 05 Mar 2026 01:00:58 +0000 [thread overview]
Message-ID: <177267245896.2463633.15444204983938498113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260302181432.1836150-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 2 Mar 2026 18:14:25 +0000 you wrote:
> This series adds rps_tag_ptr which encodes both a pointer
> and a size of a power-of-two hash table in a single long word.
>
> RFS hash tables (global and per rx-queue) are converted to rps_tag_ptr.
>
> This removes a cache line miss, and allows high-order allocations.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/7] net: add rps_tag_ptr type and helpers
https://git.kernel.org/netdev/net-next/c/42a101775bc5
- [v3,net-next,2/7] net-sysfs: remove rcu field from 'struct rps_sock_flow_table'
https://git.kernel.org/netdev/net-next/c/61753849b8bc
- [v3,net-next,3/7] net-sysfs: add rps_sock_flow_table_mask() helper
https://git.kernel.org/netdev/net-next/c/9cde131cdd88
- [v3,net-next,4/7] net-sysfs: use rps_tag_ptr and remove metadata from rps_sock_flow_table
https://git.kernel.org/netdev/net-next/c/dd378109d20f
- [v3,net-next,5/7] net-sysfs: get rid of rps_dev_flow_lock
https://git.kernel.org/netdev/net-next/c/68b6394a220b
- [v3,net-next,6/7] net-sysfs: remove rcu field from 'struct rps_dev_flow_table'
https://git.kernel.org/netdev/net-next/c/b2cc61857e3c
- [v3,net-next,7/7] net-sysfs: use rps_tag_ptr and remove metadata from rps_dev_flow_table
https://git.kernel.org/netdev/net-next/c/a435163d3100
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-03-05 1:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 18:14 [PATCH v3 net-next 0/7] rfs: use high-order allocations for hash tables Eric Dumazet
2026-03-02 18:14 ` [PATCH v3 net-next 1/7] net: add rps_tag_ptr type and helpers Eric Dumazet
2026-03-03 19:47 ` Kuniyuki Iwashima
2026-03-02 18:14 ` [PATCH v3 net-next 2/7] net-sysfs: remove rcu field from 'struct rps_sock_flow_table' Eric Dumazet
2026-03-03 19:24 ` Kuniyuki Iwashima
2026-03-02 18:14 ` [PATCH v3 net-next 3/7] net-sysfs: add rps_sock_flow_table_mask() helper Eric Dumazet
2026-03-03 19:28 ` Kuniyuki Iwashima
2026-03-02 18:14 ` [PATCH v3 net-next 4/7] net-sysfs: use rps_tag_ptr and remove metadata from rps_sock_flow_table Eric Dumazet
2026-03-03 19:46 ` Kuniyuki Iwashima
2026-03-02 18:14 ` [PATCH v3 net-next 5/7] net-sysfs: get rid of rps_dev_flow_lock Eric Dumazet
2026-03-03 19:48 ` Kuniyuki Iwashima
2026-03-02 18:14 ` [PATCH v3 net-next 6/7] net-sysfs: remove rcu field from 'struct rps_dev_flow_table' Eric Dumazet
2026-03-03 19:49 ` Kuniyuki Iwashima
2026-03-02 18:14 ` [PATCH v3 net-next 7/7] net-sysfs: use rps_tag_ptr and remove metadata from rps_dev_flow_table Eric Dumazet
2026-03-03 20:06 ` Kuniyuki Iwashima
2026-03-05 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=177267245896.2463633.15444204983938498113.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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