From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>
Cc: "David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Quentin Monnet <quentin.monnet@netronome.com>
Subject: Re: [PATCH net-next V4 0/3] tools: bpftool: show filenames of pinned objects
Date: Wed, 8 Nov 2017 07:11:07 -0800 [thread overview]
Message-ID: <20171108071107.6c52f885@cakuba> (raw)
In-Reply-To: <20171108045549.5356-1-bhole_prashant_q7@lab.ntt.co.jp>
On Wed, 8 Nov 2017 13:55:46 +0900, Prashant Bhole wrote:
> This patchset adds support to show pinned objects in object details.
>
> Patch1 adds a funtionality to open a path in bpf-fs regardless of its object
> type.
>
> Patch2 adds actual functionality by scanning the bpf-fs once and adding
> object information in hash table, with object id as a key. One object may be
> associated with multiple paths because an object can be pinned multiple times
>
> Patch3 adds command line option to enable this functionality. Making it optional
> because scanning bpf-fs can be costly.
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Thank you!
next prev parent reply other threads:[~2017-11-08 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 4:55 [PATCH net-next V4 0/3] tools: bpftool: show filenames of pinned objects Prashant Bhole
2017-11-08 4:55 ` [PATCH net-next V4 1/3] tools: bpftool: open pinned object without type check Prashant Bhole
2017-11-08 4:55 ` [PATCH net-next V4 2/3] tools: bpftool: show filenames of pinned objects Prashant Bhole
2017-11-08 4:55 ` [PATCH net-next V4 3/3] tools: bpftool: optionally " Prashant Bhole
2017-11-08 15:11 ` Jakub Kicinski [this message]
2017-11-11 4:05 ` [PATCH net-next V4 0/3] tools: bpftool: " David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171108071107.6c52f885@cakuba \
--to=jakub.kicinski@netronome.com \
--cc=ast@kernel.org \
--cc=bhole_prashant_q7@lab.ntt.co.jp \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=quentin.monnet@netronome.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).