Netdev List
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@kernel.org, horms@kernel.org
Subject: Re: [PATCH net-next 1/2] ipv4: Store netns in FIB table
Date: Wed, 14 Oct 2026 07:36:35 -0600	[thread overview]
Message-ID: <cd9e9a7e-c4aa-49ec-915b-ce472e7d7dfb@kernel.org> (raw)
In-Reply-To: <20261014082612.1280756-2-idosch@nvidia.com>

On 10/14/26 2:26 AM, Ido Schimmel wrote:
> The next patch will stop passing the network namespace to
> fib_table_lookup() and instead pass the namespace from the FIB table to
> the fib_table_lookup tracepoint. As a preparation, store the namespace
> in the FIB table when the table is created.
> 
> The FIB table structure grows from 48 bytes to 56 bytes and still fits
> in a single cache line.
> 
> No functional changes intended.
> 
> Assisted-by: LLM
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
>  include/net/ip_fib.h    | 4 +++-
>  net/ipv4/fib_frontend.c | 6 +++---
>  net/ipv4/fib_trie.c     | 6 ++++--
>  3 files changed, 10 insertions(+), 6 deletions(-)
> 

Reviewed-by: David Ahern <dsahern@kernel.org>



  reply	other threads:[~2026-10-14 13:36 UTC|newest]

Thread overview: 6+ 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 [this message]
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

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=cd9e9a7e-c4aa-49ec-915b-ce472e7d7dfb@kernel.org \
    --to=dsahern@kernel.org \
    --cc=davem@davemloft.net \
    --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