From: David Ahern <dsahern@gmail.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org,
Stephen Hemminger <sthemmin@microsoft.com>,
Daniel Borkmann <borkmann@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH net-next] net: add network device notifier trace points
Date: Wed, 19 Dec 2018 09:48:22 -0700 [thread overview]
Message-ID: <bca7120f-c574-2def-0fcc-85fc33c630c3@gmail.com> (raw)
In-Reply-To: <20181219083643.7f724e59@redhat.com>
On 12/19/18 12:36 AM, Jesper Dangaard Brouer wrote:
> Today, the existing network tracepoints using dev->name is not that
> usable by BPF, as BPF cannot identify the interface. Thus IMHO it would
> make sense to convert the existing network tracepoints dev->name into
> dev->ifindex, and then let perf-script convert this to the interface
> name. Either in userspace via if_indextoname(3), or (as ACME pointed
> out at the time) we might want to have a lookup table stored together
> with perf.data for later inspection (in-case ifindexes changed).
>
You need network namespace references as well and the ability to monitor
device notifications.
prev parent reply other threads:[~2018-12-19 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 2:27 [PATCH net-next] net: add network device notifier trace points Stephen Hemminger
2018-12-19 3:38 ` David Ahern
2018-12-19 7:36 ` Jesper Dangaard Brouer
2018-12-19 15:43 ` Stephen Hemminger
2018-12-19 15:46 ` Daniel Borkmann
2018-12-19 16:40 ` Jesper Dangaard Brouer
2018-12-19 16:55 ` Steven Rostedt
2018-12-19 17:07 ` Daniel Borkmann
2018-12-19 15:51 ` Steven Rostedt
2018-12-19 16:48 ` David Ahern [this message]
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=bca7120f-c574-2def-0fcc-85fc33c630c3@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=borkmann@iogearbox.net \
--cc=brouer@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).