All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Fomichev <sdf@fomichev.me>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	sdf@google.com
Subject: [LSF/MM ATTEND] BPF track
Date: Thu, 21 Feb 2019 11:08:50 -0800	[thread overview]
Message-ID: <20190221190850.GE1928@mini-arch> (raw)

Hi,

I'd like to participate in the BPF track of LSF/MM Summit 2019. I work
on BPF stuff at Google, I recently contributed to bpftool and BPF
selftests.

Topics I'd like to discuss:
* next steps for BPF flow dissector and how to reach feature parity with
  the C-based one (see my recent RFC)
* how to extend BPF test framework with additional metadata (we had a
  brief conversation about that at LPC)

I don't think my topics deserve a dedicated 30-minutes session, I just
like to talk to people in the hallway :-)

I'm also interested in general BPF direction and how we can apply future
potential features here at Google.

             reply	other threads:[~2019-02-21 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 19:08 Stanislav Fomichev [this message]
2019-02-21 21:58 [LSF/MM ATTEND] BPF track Joe Stringer
2019-03-12 16:01 Lorenz Bauer

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=20190221190850.GE1928@mini-arch \
    --to=sdf@fomichev.me \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=sdf@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.