From: Alexei Starovoitov <ast@plumgrid.com>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] bpf: BPF based latency tracing
Date: Fri, 19 Jun 2015 17:53:57 -0700 [thread overview]
Message-ID: <5584B9A5.9030602@plumgrid.com> (raw)
In-Reply-To: <1434722444-10200-1-git-send-email-daniel.wagner@bmw-carit.de>
On 6/19/15 7:00 AM, Daniel Wagner wrote:
> BPF offers another way to generate latency histograms. We attach
> kprobes at trace_preempt_off and trace_preempt_on and calculate the
> time it takes to from seeing the off/on transition.
...
> Signed-off-by: Daniel Wagner <daniel.wagner@bmw-carit.de>
...
> With the rebase on net-next no additinal patches are needed and this
> thing here runs fine.
...
> samples/bpf/Makefile | 4 ++
> samples/bpf/lathist_kern.c | 99 +++++++++++++++++++++++++++++++++++++++++++
> samples/bpf/lathist_user.c | 103 +++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 206 insertions(+)
> create mode 100644 samples/bpf/lathist_kern.c
> create mode 100644 samples/bpf/lathist_user.c
Thanks. That's a useful example.
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
Dave,
this patch is for net-next and I hope it's not too late
for this merge window.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-06-20 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 14:00 [PATCH v2] bpf: BPF based latency tracing Daniel Wagner
2015-06-20 0:53 ` Alexei Starovoitov [this message]
2015-06-23 13:10 ` David Miller
2015-06-20 8:14 ` Daniel Borkmann
2015-06-22 7:34 ` Daniel Wagner
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=5584B9A5.9030602@plumgrid.com \
--to=ast@plumgrid.com \
--cc=daniel.wagner@bmw-carit.de \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
/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