mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: "lsf-pc@lists.linux-foundation.org" 
	<lsf-pc@lists.linux-foundation.org>, bpf <bpf@vger.kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [LSF/MM/BPF TOPIC] ls+cat based debugging for BPF
Date: Fri, 24 Jan 2020 21:25:22 +0000	[thread overview]
Message-ID: <A8AB5F56-7233-40AD-9C49-2348B708557B@fb.com> (raw)

ls+cat based debugging for BPF
================================

Currently, users monitor/debug BPF programs and maps via sys_bpf(). This
approach is different to the habit of some system admins, who do these
works via ls+cat in sysfs. In this LSF/MM/BPF, we would like to discuss
whether/how to enable similar debugging interface for BPF programs and 
maps. Specifically, we can discuss:

  1) What inforamtions to show in sysfs/bpffs;
  2) Granularity to enable/disable these information;
  3) Will there be any overhead? If so, how much overhead is acceptable.

These discussions should save us a lot of time over emails. 

I will share a prototype of this before LSF/MM/BPF.

Thanks,
Song

                 reply	other threads:[~2020-01-24 21:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=A8AB5F56-7233-40AD-9C49-2348B708557B@fb.com \
    --to=songliubraving@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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

all inboxes | Powered by JetHome®