[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM0EoM=sbtTUwPZd7QsApqQh-WxQxQ0Ecw1YR4GHu87vmunqvw@mail.gmail.com>
Date: Sun, 29 Jan 2023 06:19:42 -0500
From: Jamal Hadi Salim <jhs@...atatu.com>
To: John Fastabend <john.fastabend@...il.com>
Cc: Willem de Bruijn <willemb@...gle.com>,
Stanislav Fomichev <sdf@...gle.com>,
Jamal Hadi Salim <hadi@...atatu.com>,
Jiri Pirko <jiri@...nulli.us>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
kernel@...atatu.com, deb.chatterjee@...el.com,
anjali.singhai@...el.com, namrata.limaye@...el.com,
khalidm@...dia.com, tom@...anda.io, pratyush@...anda.io,
xiyou.wangcong@...il.com, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, vladbu@...dia.com, simon.horman@...igine.com,
stefanc@...vell.com, seong.kim@....com, mattyk@...dia.com,
dan.daly@...el.com, john.andy.fingerhut@...el.com
Subject: Re: [PATCH net-next RFC 00/20] Introducing P4TC
Sorry, John - to answer your question on P4runtime; that runs on top
of netlink. Netlink can express
a lot more than P4runtime so we are letting it sit in userspace. I
could describe the netlink interfaces but easier if you look at the
code and ping me privately unless there are more folks interested in
that to which i can respond on the list.
cheers,
jamal
On Sun, Jan 29, 2023 at 6:11 AM Jamal Hadi Salim <jhs@...atatu.com> wrote:
>
> On Sun, Jan 29, 2023 at 12:39 AM John Fastabend
> <john.fastabend@...il.com> wrote:
> >
> > Willem de Bruijn wrote:
> > > On Sat, Jan 28, 2023 at 10:10 AM Jamal Hadi Salim <jhs@...atatu.com> wrote:
> > > >
> >
> > [...]
> >
> >
> > Also there already exists a P4 backend that targets BPF.
> >
> > https://github.com/p4lang/p4c
>
> There's also one based on rust - does that mean we should rewrite our
> code in rust?
> Joking aside - rust was a suggestion made at a talk i did. I ended up
> adding a slide for the next talk which read:
>
> Title: So... how is this better than KDE?
> Attributed to Rusty Russell
> Who attributes it to Cort Dougan
> s/KDE/[rust/ebpf/dpdk/vpp/ovs]/g
>
> We have very specific goals - of which the most important is met by
> what works today and we are reusing that.
>
> cheers,
> jamal
>
> > So as a SW object we can just do the P4 compilation step in user
> > space and run it in BPF as suggested. Then for hw offload we really
> > would need to see some hardware to have any concrete ideas on how
> > to make it work.
> >
>
>
> > Also P4 defines a runtime API so would be good to see how all that
> > works with any proposed offload.
Powered by blists - more mailing lists