[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aPi1z_frpBzpBPpa@shredder>
Date: Wed, 22 Oct 2025 13:45:35 +0300
From: Ido Schimmel <idosch@...sch.org>
To: Tonghao Zhang <tonghao@...aicloud.com>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
Eran Ben Elisha <eranbe@...lanox.com>,
Jiri Pirko <jiri@...lanox.com>,
Cong Wang <xiyou.wangcong@...il.com>
Subject: Re: [PATCH net-next] net: add the ifindex for
trace_net_dev_xmit_timeout
On Wed, Oct 22, 2025 at 04:31:34PM +0800, Tonghao Zhang wrote:
> > On Oct 22, 2025, at 08:10, Jakub Kicinski <kuba@...nel.org> wrote:
> >
> > On Tue, 21 Oct 2025 17:19:00 +0800 Tonghao Zhang wrote:
> >> In a multi-network card or container environment, provide more accurate information.
> >
> > Why do you think that ifindex is more accurate than the name?
> > Neither is unique with netns..
> I thought ifindex was globally unique, but in fact, different namespaces may have the same ifindex value. What about adding the ns.inum inode ?
The netns cookie is probably better. See this thread:
https://lore.kernel.org/netdev/c28ded3224734ca62187ed9a41f7ab39ceecb610.camel@fejes.dev/
You can also retrieve it by attaching a BPF program to the tracepoint.
Powered by blists - more mailing lists