[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/KFIBLicHQ+Am5R@pop-os.localdomain>
Date: Sun, 19 Feb 2023 12:22:56 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Yonghong Song <yhs@...a.com>
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org,
Cong Wang <cong.wang@...edance.com>,
John Fastabend <john.fastabend@...il.com>,
Jakub Sitnicki <jakub@...udflare.com>
Subject: Re: [Patch net-next] sock_map: dump socket map id via diag
On Sun, Feb 12, 2023 at 10:29:11PM -0800, Yonghong Song wrote:
>
>
> On 2/11/23 12:19 PM, Cong Wang wrote:
> > From: Cong Wang <cong.wang@...edance.com>
> >
> > Currently there is no way to know which sockmap a socket has been added
> > to from outside, especially for that a socket can be added to multiple
> > sockmap's. We could dump this via socket diag, as shown below.
> >
> > Sample output:
> >
> > # ./iproute2/misc/ss -tnaie --sockmap
> > ESTAB 0 344329 127.0.0.1:1234 127.0.0.1:40912 ino:21098 sk:5 cgroup:/user.slice/user-0.slice/session-c1.scope <-> sockmap: 1
> >
> > # bpftool map
> > 1: sockmap flags 0x0
> > key 4B value 4B max_entries 2 memlock 4096B
> > pids echo-sockmap(549)
> > 4: array name pid_iter.rodata flags 0x480
> > key 4B value 4B max_entries 1 memlock 4096B
> > btf_id 10 frozen
> > pids bpftool(624)
> >
> > In the future, we could dump other sockmap related stats too, hence I
> > make it a nested attribute.
>
> Have you considered to implement a sockmap iterator? This will be
I think you understand it wrong, I don't want to dump the map, please
double check the above requirement.
Thanks.
Powered by blists - more mailing lists