All of lore.kernel.org
 help / color / mirror / Atom feed
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, rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com, daniel@iogearbox.net,
	petrm@nvidia.com, ferenc@fejes.dev
Subject: Re: [PATCH net-next v2 0/3] Report netns cookie in FIB lookup tracepoints
Date: Tue, 13 Oct 2026 10:40:05 +0000	[thread overview]
Message-ID: <179188800577.210833.13706895255027341041.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008133158.1438907-1-idosch@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Thu,  8 Oct 2026 16:31:55 +0300 you wrote:
> The fib:fib_table_lookup and fib6:fib6_table_lookup tracepoints do not
> report the network namespace in which the lookup was performed, so
> lookups performed in different namespaces cannot be told apart. The
> recorded PID does not help either, as lookups in the receive path are
> performed in softIRQ context.
> 
> This is a problem, for example, for netns-aware tracers [1] and
> multi-ASIC systems where each ASIC and its ports reside in a separate
> network namespace.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/3] ipv6: Report netns cookie in fib6_table_lookup tracepoint
    https://git.kernel.org/netdev/net-next/c/ffe378c06c10
  - [net-next,v2,2/3] ipv4: Pass netns to fib_table_lookup()
    https://git.kernel.org/netdev/net-next/c/c436a624f89e
  - [net-next,v2,3/3] ipv4: Report netns cookie in fib_table_lookup tracepoint
    https://git.kernel.org/netdev/net-next/c/a780f51d5bc8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-13 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 13:31 [PATCH net-next v2 0/3] Report netns cookie in FIB lookup tracepoints Ido Schimmel
2026-10-08 13:31 ` [PATCH net-next v2 1/3] ipv6: Report netns cookie in fib6_table_lookup tracepoint Ido Schimmel
2026-10-10 13:33   ` David Ahern
2026-10-08 13:31 ` [PATCH net-next v2 2/3] ipv4: Pass netns to fib_table_lookup() Ido Schimmel
2026-10-10 13:34   ` David Ahern
2026-10-08 13:31 ` [PATCH net-next v2 3/3] ipv4: Report netns cookie in fib_table_lookup tracepoint Ido Schimmel
2026-10-10 13:34   ` David Ahern
2026-10-13 10:25 ` [PATCH net-next v2 0/3] Report netns cookie in FIB lookup tracepoints Paolo Abeni
2026-10-13 17:45   ` Ido Schimmel
2026-10-13 10: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=179188800577.210833.13706895255027341041.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@kernel.org \
    --cc=ferenc@fejes.dev \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=rostedt@goodmis.org \
    /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.