mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Song Chen <chensong_2000@189.cn>,
	ast@kernel.org, andrii@kernel.org, kafai@fb.com,
	songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
	kpsingh@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] sample: bpf: introduce irqlat
Date: Thu, 14 Apr 2022 11:47:45 +0200	[thread overview]
Message-ID: <2e6ee265-903c-2b5c-aefd-ec24f930c999@iogearbox.net> (raw)
In-Reply-To: <1649927240-18991-1-git-send-email-chensong_2000@189.cn>

On 4/14/22 11:07 AM, Song Chen wrote:
> I'm planning to implement a couple of ebpf tools for preempt rt,
> including irq latency, preempt latency and so on, how does it sound
> to you?

Sounds great, thanks! Please add these tools for upstream inclusion either to bpftrace [0] or
bcc [1], then a wider range of users would be able to benefit from them as well as they are
also shipped as distro packages and generally more widely used compared to kernel samples.

Thanks Song!

   [0] https://github.com/iovisor/bpftrace/tree/master/tools
   [1] https://github.com/iovisor/bcc/tree/master/libbpf-tools

> Song Chen (1):
>    sample: bpf: introduce irqlat
> 
>   samples/bpf/.gitignore    |   1 +
>   samples/bpf/Makefile      |   5 ++
>   samples/bpf/irqlat_kern.c |  81 ++++++++++++++++++++++++++++++
>   samples/bpf/irqlat_user.c | 100 ++++++++++++++++++++++++++++++++++++++
>   4 files changed, 187 insertions(+)
>   create mode 100644 samples/bpf/irqlat_kern.c
>   create mode 100644 samples/bpf/irqlat_user.c
> 


  reply	other threads:[~2022-04-14  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  9:07 Song Chen
2022-04-14  9:47 ` Daniel Borkmann [this message]
2022-04-14 11:25   ` Song Chen
2022-04-14 15:32     ` Daniel Borkmann
2022-04-15  1:58       ` Song Chen

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=2e6ee265-903c-2b5c-aefd-ec24f930c999@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=chensong_2000@189.cn \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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

all inboxes | Powered by JetHome®