From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@kernel.org, dsahern@kernel.org,
horms@kernel.org
Subject: Re: [PATCH net-next 0/2] ipv4: Remove netns argument from fib_table_lookup()
Date: Sat, 17 Oct 2026 02:00:05 +0000 [thread overview]
Message-ID: <179220240552.1058620.10450295801123957981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261014082612.1280756-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 14 Oct 2026 11:26:10 +0300 you wrote:
> Commit c436a624f89e ("ipv4: Pass netns to fib_table_lookup()") added the
> network namespace as an argument of fib_table_lookup() so that it could
> be passed to the fib_table_lookup tracepoint. As noted by Paolo [1], the
> function is called in the data path where the additional argument is
> unnecessary overhead, as the namespace is only needed when the
> tracepoint is enabled.
>
> [...]
Here is the summary with links:
- [net-next,1/2] ipv4: Store netns in FIB table
https://git.kernel.org/netdev/net-next/c/1b82d5ce3ba9
- [net-next,2/2] ipv4: Do not pass netns to fib_table_lookup()
https://git.kernel.org/netdev/net-next/c/a25a51258acf
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-10-17 2:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 8:26 [PATCH net-next 0/2] ipv4: Remove netns argument from fib_table_lookup() Ido Schimmel
2026-10-14 8:26 ` [PATCH net-next 1/2] ipv4: Store netns in FIB table Ido Schimmel
2026-10-14 13:36 ` David Ahern
2026-10-14 8:26 ` [PATCH net-next 2/2] ipv4: Do not pass netns to fib_table_lookup() Ido Schimmel
2026-10-14 13:36 ` David Ahern
2026-10-14 9:58 ` [PATCH net-next 0/2] ipv4: Remove netns argument from fib_table_lookup() Björn Töpel
2026-10-17 2: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=179220240552.1058620.10450295801123957981.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--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