public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: lsf-pc@lists.linuxfoundation.org
Cc: bpf@vger.kernel.org, david.faust@oracle.com,
	elena.zannoni@oracle.com,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	James Hilliard <james.hilliard1@gmail.com>,
	Yonghong Song <yhs@fb.com>,
	ndesaulniers@google.com
Subject: LSF/MM/BPF activity proposal: Compiled BPF
Date: Mon, 30 Jan 2023 18:47:11 +0100	[thread overview]
Message-ID: <87edrbhq3k.fsf@oracle.com> (raw)


Hello.

We would like to suggest to the LSF/MM/BPF organization to have a
working session on "compiled BPF", i.e. on the part of BPF that involves
compilers and linkers.  This mainly involves the two mainstream
compilers that target BPF: clang and GCC, but other BPF toolchains are
slowly appearing (like the Rust compiler) and that makes it even more
important to consolidate compiled BPF.

Examples of topics to cover are the covergence of the support in both
clang/llvm and GCC, several aspects of the ABI that need to be
discussed/clarified/decided in order to avoid undefined compiler
behavior and divergences, issues related to the BPF standarization, and
suggestions on how to lift some of the existing limitations impacting
BPF C programs.

The goal is to reach agreements about particular things, document the
agreements, stick to them, and a clear plan to implement whatever is
needed in the respective compilers/tools.

Potential participants in case the activity takes place:

- Both David Faust (GNU toolchain, BPF port hacker) and myself (GNU
  toolchain, BPF port maintainer) are willing to attend the event,
  prepare discussion material, organize and participate in the
  discussions.

- Nick Desaulniers (LLVM maintainer) is also interested in attending and
  participating, provided other compromises he has in May don't get in
  the way.

- More? (Please add yourself to this list by replying to this email in
  case you are interested.)

Would the BPF community and the LSF/MM/BPF organization be interested in
having such an activity?

             reply	other threads:[~2023-01-30 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 17:47 Jose E. Marchesi [this message]
2023-01-31 19:52 ` [Lsf-pc] LSF/MM/BPF activity proposal: Compiled BPF Daniel Borkmann
2023-01-31 23:09   ` Jose E. Marchesi
2023-02-01  7:54     ` Yonghong Song

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=87edrbhq3k.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=david.faust@oracle.com \
    --cc=elena.zannoni@oracle.com \
    --cc=james.hilliard1@gmail.com \
    --cc=lsf-pc@lists.linuxfoundation.org \
    --cc=ndesaulniers@google.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