From: Stanislav Fomichev <sdf@fomichev.me>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org
Subject: [LSF/MM/BPF ATTEND] BPF track
Date: Fri, 7 Feb 2020 08:41:07 -0800 [thread overview]
Message-ID: <20200207164107.GA1400227@mini-arch> (raw)
Hi,
I'd like to participate in the BPF track of LSF/MM/BPF Summit 2020. I
work on BPF stuff at Google, I recently contributed the following
features to the upstream BPF subsystem:
* {set,get}sockopt hooks & BPF_SOCK_OPS_RTT_CB callback
* Optional socket storage cloning on accept (BPF_F_CLONE)
* Improvements to flow dissector BPF hook to make it work in driver
(non-skb) context
* Various improvements to selftests / BPF_PROG_TEST_RUN framework
Topics I'd like to discuss:
* BTF/BPF meta-information: how to append enough info to BPF/BTF to
recover build timestamp + commit sha1
* Global mode for cgroup storage as a way to have common/persistent
per-cgroup scratch buffer
* Unit-testing and uBPF; uBPF integration with libbpf
* Average prog runtime; discuss any future plans to extend it to return a
distribution, not average (with BPF?)
I don't think my topics deserve a dedicated 30-minutes session. I'm also
interested in general BPF direction and how we can apply future
potential features here at Google.
In particular, some of the proposed talks that are of particular
interest:
* BPF logging
* BPF unit testing
reply other threads:[~2020-02-07 16:41 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=20200207164107.GA1400227@mini-arch \
--to=sdf@fomichev.me \
--cc=bpf@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