All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>, John Fastabend <john.fastabend@gmail.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
	Willem de Bruijn <willemb@google.com>,
	Stanislav Fomichev <sdf@google.com>,
	Jamal Hadi Salim <hadi@mojatatu.com>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, kernel@mojatatu.com,
	deb.chatterjee@intel.com, anjali.singhai@intel.com,
	namrata.limaye@intel.com, khalidm@nvidia.com, tom@sipanda.io,
	pratyush@sipanda.io, xiyou.wangcong@gmail.com,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	vladbu@nvidia.com, simon.horman@corigine.com,
	stefanc@marvell.com, seong.kim@amd.com, mattyk@nvidia.com,
	dan.daly@intel.com, john.andy.fingerhut@intel.com
Subject: Re: [PATCH net-next RFC 00/20] Introducing P4TC
Date: Mon, 30 Jan 2023 12:26:58 +0100	[thread overview]
Message-ID: <87pmawxny5.fsf@toke.dk> (raw)
In-Reply-To: <Y9eYNsklxkm8CkyP@nanopsycho>

Jiri Pirko <jiri@resnulli.us> writes:

>>P4TC as SW/HW running same P4:
>>
>>1. This doesn't need to be done in kernel. If one compiler runs
>>   P4 into XDP or TC-BPF that is good and another compiler runs
>>   it into hw specific backend. This satisifies having both
>>   software and hardware implementation.
>>
>>Extra commentary: I agree we've been chatting about this for a long
>>time but until some vendor (Intel?) will OSS and support a linux
>>driver and hardware with open programmable parser and MAT. I'm not
>>sure how we get P4 for Linux users. Does it exist and I missed it?
>
>
> John, I think that your summary is quite accurate. Regarding SW
> implementation, I have to admit I also fail to see motivation to have P4
> specific datapath instead of having XDP/eBPF one, that could run P4
> compiled program. The only motivation would be that if somehow helps to
> offload to HW. But can it?

According to the slides from the netdev talk[0], it seems that
offloading will have to have a component that goes outside of TC anyway
(see "Model 3: Joint loading" where it says "this is impossible"). So I
don't really see why having this interpreter in TC help any.

Also, any control plane management feature specific to managing P4 state
in hardware could just as well manage a BPF-based software path on the
kernel side instead of the P4 interpreter stuff...

-Toke

[0] https://netdevconf.info/0x16/session.html?Your-Network-Datapath-Will-Be-P4-Scripted


  reply	other threads:[~2023-01-30 11:27 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 17:03 [PATCH net-next RFC 00/20] Introducing P4TC Jamal Hadi Salim
2023-01-26 23:30 ` Jakub Kicinski
2023-01-27 13:33   ` Jamal Hadi Salim
2023-01-27 17:18     ` Jakub Kicinski
2023-01-27 19:42       ` Jamal Hadi Salim
2023-01-28  1:34         ` Singhai, Anjali
2023-01-28 21:17           ` Tom Herbert
2023-01-29  2:09             ` Stephen Hemminger
2023-01-30  3:09             ` Singhai, Anjali
2023-01-30 17:05               ` Tom Herbert
2023-01-27 18:26   ` Jiri Pirko
2023-01-27 20:04     ` Jamal Hadi Salim
2023-01-27 22:26       ` sdf
2023-01-27 23:06         ` Tom Herbert
2023-01-28  0:47           ` Stanislav Fomichev
2023-01-28  1:32             ` Tom Herbert
2023-01-27 23:27         ` Jamal Hadi Salim
2023-01-28  0:47           ` Stanislav Fomichev
2023-01-28 13:37             ` Willem de Bruijn
2023-01-28 15:10               ` Jamal Hadi Salim
2023-01-28 15:33                 ` Willem de Bruijn
2023-01-29  5:39                   ` John Fastabend
2023-01-29 11:11                     ` Jamal Hadi Salim
2023-01-29 11:19                       ` Jamal Hadi Salim
2023-01-30  4:30                       ` John Fastabend
2023-01-30 10:13                         ` Jiri Pirko
2023-01-30 11:26                           ` Toke Høiland-Jørgensen [this message]
2023-01-30 14:06                             ` Jamal Hadi Salim
2023-01-30 14:42                               ` Andrew Lunn
2023-01-30 15:31                                 ` Jamal Hadi Salim
2023-01-30 17:04                               ` Toke Høiland-Jørgensen
2023-01-30 19:02                                 ` Jamal Hadi Salim
2023-01-30 20:21                                   ` Toke Høiland-Jørgensen
2023-01-30 21:10                                     ` John Fastabend
2023-01-30 21:20                                       ` Toke Høiland-Jørgensen
2023-01-30 22:53                                         ` Jamal Hadi Salim
2023-01-30 23:24                                           ` Singhai, Anjali
2023-01-31  0:06                                             ` John Fastabend
2023-01-31  0:26                                               ` Jamal Hadi Salim
2023-01-31  4:12                                                 ` Jakub Kicinski
2023-01-31 10:27                                                   ` Jamal Hadi Salim
2023-01-31 10:30                                                     ` Jamal Hadi Salim
2023-01-31 19:10                                                       ` Jakub Kicinski
2023-01-31 22:32                                                         ` Jamal Hadi Salim
2023-01-31 22:36                                                           ` Jakub Kicinski
2023-01-31 22:50                                                             ` Jamal Hadi Salim
2023-01-30 23:32                                           ` John Fastabend
2023-01-31 12:17                                           ` Toke Høiland-Jørgensen
2023-01-31 12:37                                             ` Jiri Pirko
2023-01-31 14:38                                             ` Jiri Pirko
2023-01-31 17:01                                               ` Toke Høiland-Jørgensen
2023-01-31 22:23                                                 ` Jamal Hadi Salim
2023-01-31 22:53                                                   ` Toke Høiland-Jørgensen
2023-01-31 23:31                                                     ` Jamal Hadi Salim
2023-02-01 18:08                                                       ` Toke Høiland-Jørgensen
2023-02-02 18:50                                                         ` Jamal Hadi Salim
2023-02-02 23:34                                                           ` Tom Herbert
2023-01-30 22:41                                       ` Tom Herbert
2023-02-14 17:07                               ` Edward Cree
2023-02-14 20:44                                 ` Jamal Hadi Salim
2023-02-16 20:24                                   ` Jamal Hadi Salim
2023-01-29 11:02                   ` Jamal Hadi Salim
2023-01-29 22:14                     ` Toke Høiland-Jørgensen
2023-01-28 13:41             ` Jamal Hadi Salim
2023-01-27 23:02       ` Daniel Borkmann
2023-01-27 23:57         ` Jamal Hadi Salim

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=87pmawxny5.fsf@toke.dk \
    --to=toke@redhat.com \
    --cc=anjali.singhai@intel.com \
    --cc=dan.daly@intel.com \
    --cc=davem@davemloft.net \
    --cc=deb.chatterjee@intel.com \
    --cc=edumazet@google.com \
    --cc=hadi@mojatatu.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=john.andy.fingerhut@intel.com \
    --cc=john.fastabend@gmail.com \
    --cc=kernel@mojatatu.com \
    --cc=khalidm@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mattyk@nvidia.com \
    --cc=namrata.limaye@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pratyush@sipanda.io \
    --cc=sdf@google.com \
    --cc=seong.kim@amd.com \
    --cc=simon.horman@corigine.com \
    --cc=stefanc@marvell.com \
    --cc=tom@sipanda.io \
    --cc=vladbu@nvidia.com \
    --cc=willemb@google.com \
    --cc=xiyou.wangcong@gmail.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 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.