From: dthaler1968@googlemail.com
To: "'Alexei Starovoitov'" <alexei.starovoitov@gmail.com>,
"'David Vernet'" <void@manifault.com>
Cc: "'Dave Thaler'" <dthaler1968@googlemail.com>, <bpf@ietf.org>,
"'bpf'" <bpf@vger.kernel.org>,
"'Jakub Kicinski'" <kuba@kernel.org>
Subject: RE: [Bpf] BPF ISA conformance groups
Date: Tue, 19 Dec 2023 10:15:12 -0800 [thread overview]
Message-ID: <09e101da32a7$4f749aa0$ee5dcfe0$@gmail.com> (raw)
In-Reply-To: <CAADnVQJ-JwNTY5fW-oXdTur9aDrv2NQoreTH3yYZemVBVtq9fQ@mail.gmail.com>
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
[...]
> > Well, maybe not for Netronome, or maybe not even for any vendor
> > (though we have no way of knowing that yet), but what about for other
> > contexts like Windows / Linux cross-platform compat?
>
> bpf on windows started similar to netronome. The goal was to demonstrate
> real cilium progs running on windows. And it was done.
The eBPF for Windows project's origin was independent of Cilium per se.
The goal was to enable us to write BPF programs that worked on both Windows
and Linux, rather than doing similar work separately which would double the work.
Once the work was far enough along, Cilium then became an interesting test case
to use in a demo since it was popular and recognizeable.
Dave
WARNING: multiple messages have this Message-ID (diff)
From: dthaler1968=40googlemail.com@dmarc.ietf.org
To: "'Alexei Starovoitov'" <alexei.starovoitov@gmail.com>,
"'David Vernet'" <void@manifault.com>
Cc: "'Dave Thaler'" <dthaler1968@googlemail.com>, <bpf@ietf.org>,
"'bpf'" <bpf@vger.kernel.org>,
"'Jakub Kicinski'" <kuba@kernel.org>
Subject: Re: [Bpf] BPF ISA conformance groups
Date: Tue, 19 Dec 2023 10:15:12 -0800 [thread overview]
Message-ID: <09e101da32a7$4f749aa0$ee5dcfe0$@gmail.com> (raw)
Message-ID: <20231219181512.Kw24XCkTC9hDKyyzDiGrVZ8RAyURwEVFr8hGCkoq2AA@z> (raw)
In-Reply-To: <CAADnVQJ-JwNTY5fW-oXdTur9aDrv2NQoreTH3yYZemVBVtq9fQ@mail.gmail.com>
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
[...]
> > Well, maybe not for Netronome, or maybe not even for any vendor
> > (though we have no way of knowing that yet), but what about for other
> > contexts like Windows / Linux cross-platform compat?
>
> bpf on windows started similar to netronome. The goal was to demonstrate
> real cilium progs running on windows. And it was done.
The eBPF for Windows project's origin was independent of Cilium per se.
The goal was to enable us to write BPF programs that worked on both Windows
and Linux, rather than doing similar work separately which would double the work.
Once the work was far enough along, Cilium then became an interesting test case
to use in a demo since it was popular and recognizeable.
Dave
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2023-12-19 18:15 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 20:18 IETF 118 BPF WG summary David Vernet
2023-11-27 20:18 ` [Bpf] " David Vernet
2023-11-28 9:43 ` Michael Richardson
2023-11-28 9:43 ` Michael Richardson
2023-12-02 19:51 ` BPF ISA conformance groups dthaler1968
2023-12-02 19:51 ` [Bpf] " dthaler1968=40googlemail.com
2023-12-07 21:51 ` David Vernet
2023-12-07 21:51 ` David Vernet
2023-12-10 3:10 ` Alexei Starovoitov
2023-12-10 3:10 ` Alexei Starovoitov
2023-12-10 21:13 ` Watson Ladd
2023-12-10 21:13 ` Watson Ladd
2023-12-12 21:45 ` David Vernet
2023-12-12 21:45 ` David Vernet
2023-12-12 22:01 ` dthaler1968
2023-12-12 22:01 ` dthaler1968=40googlemail.com
2023-12-12 22:55 ` Alexei Starovoitov
2023-12-12 22:55 ` Alexei Starovoitov
2023-12-12 23:35 ` David Vernet
2023-12-12 23:35 ` David Vernet
2023-12-13 1:32 ` Alexei Starovoitov
2023-12-13 1:32 ` Alexei Starovoitov
2023-12-13 18:56 ` David Vernet
2023-12-13 18:56 ` David Vernet
2023-12-14 0:12 ` Alexei Starovoitov
2023-12-14 0:12 ` Alexei Starovoitov
2023-12-14 17:44 ` David Vernet
2023-12-14 17:44 ` David Vernet
2023-12-15 5:29 ` Christoph Hellwig
2023-12-15 5:29 ` Christoph Hellwig
2023-12-19 1:15 ` Alexei Starovoitov
2023-12-19 1:15 ` Alexei Starovoitov
2023-12-19 18:10 ` dthaler1968
2023-12-19 18:10 ` dthaler1968=40googlemail.com
2023-12-20 3:28 ` Alexei Starovoitov
2023-12-20 3:28 ` Alexei Starovoitov
2023-12-21 7:00 ` Christoph Hellwig
2023-12-21 7:00 ` Christoph Hellwig
2024-01-05 22:07 ` David Vernet
2024-01-05 22:07 ` David Vernet
2024-01-08 16:00 ` Christoph Hellwig
2024-01-08 21:51 ` Alexei Starovoitov
2024-01-08 21:51 ` Alexei Starovoitov
2024-01-09 11:35 ` Jose E. Marchesi
2024-01-09 11:35 ` Jose E. Marchesi
2024-01-23 21:39 ` David Vernet
2024-01-23 21:39 ` David Vernet
2024-01-23 23:29 ` dthaler1968
2024-01-23 23:29 ` dthaler1968=40googlemail.com
2024-01-25 2:55 ` Alexei Starovoitov
2024-01-25 2:55 ` Alexei Starovoitov
2024-01-09 15:26 ` Christoph Hellwig
2023-12-19 18:15 ` dthaler1968 [this message]
2023-12-19 18:15 ` dthaler1968=40googlemail.com
2023-12-13 16:59 ` Christoph Hellwig
2023-12-13 16:59 ` Christoph Hellwig
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='09e101da32a7$4f749aa0$ee5dcfe0$@gmail.com' \
--to=dthaler1968@googlemail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=void@manifault.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