On Wed, 30 May 2018 09:15:25 -0700
Song Liu wrote:
> On Tue, May 29, 2018 at 12:55 PM, Daniel Borkmann
> wrote:
> > 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 expos
On Tue, May 29, 2018 at 12:55 PM, Daniel Borkmann wrote:
> 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
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. Rig
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
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