[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c7a3a2bb-fe79-66cb-159e-b5680f53910f@iogearbox.net>
Date: Tue, 29 May 2018 21:55:09 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Jesper Dangaard Brouer <brouer@...hat.com>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH bpf-next 04/11] bpf: show prog and map id in fdinfo
On 05/29/2018 07:27 PM, Jesper Dangaard Brouer wrote:
> On Mon, 28 May 2018 02:43:37 +0200
> Daniel Borkmann <daniel@...earbox.net> wrote:
>
>> Its trivial and straight forward to expose it for scripts that can
>> then use it along with bpftool in order to inspect an individual
>> application's used maps and progs. Right now we dump some basic
>> information in the fdinfo file but with the help of the map/prog
>> id full introspection becomes possible now.
>>
>> Signed-off-by: Daniel Borkmann <daniel@...earbox.net>
>> Acked-by: Alexei Starovoitov <ast@...nel.org>
>
> AFAICR iproute uses this proc fdinfo, for pinned maps. Have you tested
> if this change is handled gracefully by tc ?
Yep, it works just fine, I also tested it before submission.
Powered by blists - more mailing lists