P4TC was first introduced in 0x16[1].

After the first RFC was posted on the list, some of the community feedback made was to convert the s/w datapath from a scriptable (ala tc u32) to instead make use of eBPF with a strong argument being made that the s/w data path will be more performant.

In this talk Jamal Hadi Salim et al will discuss the new architecture which factors in eBPF as the software datapath. The talk will go into the P4TC architecture factoring in eBPF and the pros and cons of this change from a scriptable approach. Jamal (twit that horn here) will further discuss the uapi and the kernel code architecture. There have been several RFC postings in the last 9 months[2] and it is expected the upstreaming efforts will start in the near future.

cheers, jamal

[1]https://netdevconf.info/0x16/session.html?Your-Network-Datapath-Will-Be-P4-S... [2] latest at this posting can be found here: https://lore.kernel.org/netdev/20230930143542.101000-1-jhs@mojatatu.com/