All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenz Bauer <lmb@cloudflare.com>
To: lsf-pc@lists.linux-foundation.org
Cc: Alexei Starovoitov <ast@fb.com>, bpf@vger.kernel.org
Subject: [LSF/MM ATTEND] BPF track
Date: Tue, 12 Mar 2019 16:01:37 +0000	[thread overview]
Message-ID: <CACAyw98JsBacLyjtLsj3XnikNbgNRmxhEHpRjzqdAk0=H4BbOg@mail.gmail.com> (raw)

Hello,

I'd like to attend the BPF track of LSF/MM 2019 Summit. I work on L4
load balancing at Cloudflare, which uses XDP as a key component. I've
also been involved in our XDP DoS mitigation work.

I'm working on moving the functionality of an out of tree kernel
module into tc clsact / XDP and will contribute eBPF helpers to this
effect. Checking SYN cookies, possibly integration with TPROXY, etc.
As time permits I'll keep fixing small annoyances I encounter along
the way.

My focus would be getting acquainted with other contributors to eBPF,
and sharing the experience we've had using eBPF at CF. Specifically,
hitting verifier limits when generating code due to forced inlining
and tail calling, and patching eBPF at load time to en/disable code
paths because of missing global variables. Since we use / maintain an
eBPF loader written in Go (github.com/newtools/ebpf) I'd also join the
discussion around the one true loader and how BTF specifically affects
third-party loaders.

Best
Lorenz
-- 
Lorenz Bauer  |  Systems Engineer
25 Lavington St., London SE1 0NZ

www.cloudflare.com

             reply	other threads:[~2019-03-12 16:01 UTC|newest]

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

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='CACAyw98JsBacLyjtLsj3XnikNbgNRmxhEHpRjzqdAk0=H4BbOg@mail.gmail.com' \
    --to=lmb@cloudflare.com \
    --cc=ast@fb.com \
    --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 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.