From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: [PATCH bpf-next 04/11] bpf: show prog and map id in fdinfo Date: Tue, 29 May 2018 21:55:09 +0200 Message-ID: References: <20180528004344.3606-1-daniel@iogearbox.net> <20180528004344.3606-5-daniel@iogearbox.net> <20180529192758.28240588@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: Jesper Dangaard Brouer Return-path: Received: from www62.your-server.de ([213.133.104.62]:42438 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966399AbeE2TzL (ORCPT ); Tue, 29 May 2018 15:55:11 -0400 In-Reply-To: <20180529192758.28240588@redhat.com> Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 05/29/2018 07:27 PM, Jesper Dangaard Brouer wrote: > On Mon, 28 May 2018 02:43:37 +0200 > Daniel Borkmann 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 >> Acked-by: Alexei Starovoitov > > 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.