From: David Vernet <void@manifault.com>
To: hackathon@ietf.org
Cc: bpf@ietf.org, ast@kernel.org, mykolal@meta.com, bpf@vger.kernel.org
Subject: Re: BPF Hackathon project
Date: Tue, 14 Feb 2023 16:22:01 -0600 [thread overview]
Message-ID: <Y+wJibgVRJg+8kNW@maniforge> (raw)
In-Reply-To: <Y+wFfL/ZB1aIPFTl@maniforge>
On Tue, Feb 14, 2023 at 04:04:44PM -0600, David Vernet wrote:
> Hello,
>
> I just added a new BPF hackathon project for IETF 116:
Given that Daniel and Alexei recently added a MAINTAINERS entry for the
BPF documentation and standardization effort in [0], let's add bpf@vger
to the cc list.
[0]: https://lore.kernel.org/all/57619c0dd8e354d82bf38745f99405e3babdc970.1676068387.git.daniel@iogearbox.net/
>
> **BPF***
> - Champion(s)
> - David Vernet (void@manifault.com)
> - Alexei Starovoitov (ast@kernel.org)
> - Mykola Lysenko (mykolal@meta.com)
> - Project info
> - Learn about [BPF](https://ebpf.io/what-is-ebpf/) and/or
> [Sched Ext](https://lwn.net/Articles/922405/) by writing BPF
> programs, creating custom Linux schedulers in BPF, and even
> contributing to the BPF codebase itself.
> - Add [BPF documentation]
> (https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/tree/Documentation/bpf)
> to the upstream Linux kernel tree in support of BPF standardization
> through IETF. Newcomers to Linux and BPF are welcome.
> - Write custom schedulers in BPF, using the new Sched Ext feature
> currently being [discussed upstream]
> https://lore.kernel.org/bpf/20230128001639.3510083-1-tj@kernel.org/).
>
> As stated in the description above, the project will be championed by
> myself, Alexei, and Mykola. If anyone has thoughts, feedback, or
> questions, please feel free to reach out to us!
>
> - David
parent reply other threads:[~2023-02-14 22:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Y+wFfL/ZB1aIPFTl@maniforge>]
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=Y+wJibgVRJg+8kNW@maniforge \
--to=void@manifault.com \
--cc=ast@kernel.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=hackathon@ietf.org \
--cc=mykolal@meta.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