Not much to add technically but I am very curious who named it Tofino. Tofino is a city by where I live. It is a beautiful location on the Pacific Ocean on Vancouver Island. A favorite destination for our PM Justin Trudeau. Definitely one of the top 100 beautiful places in the world. When I go there I feel stress leave my body and just enjoy the sounds of the waves crashing and the feeling of the sand on my feet melt…
Intel's Tofino P4 Software Is Now Open Source
51–60 of 81 posts
Re: Intel's Tofino P4 Software Is Now Open Source
#52Earlier quoted context omitted.
Yes, Intel canceled Tofino two years ago. I'm not complaining but it's weird that they're open sourcing the SDK now. Maybe it's to support Mount Evans.
Releasing dead software that is used only to support dead hardware?
Re: Intel's Tofino P4 Software Is Now Open Source
#53Earlier quoted context omitted.
Well. It looks like abandonning software to the community. From the "P4 workflow" described at https://p4.org/ I see mentions of compiling to x86, but no mention of ARM, and no mention of BPF. So, as someone who discover it, I wonder if this project is still relevant in 2025.
Is x86 dead for wire powered devices? Regardless, OSS is probably the best way to get it onto other architectures.
Re: Intel's Tofino P4 Software Is Now Open Source
#54Earlier quoted context omitted.
What are they making instead?
To my knowledge: nothing. Intel is exiting the network switch silicon business¹. Broadcom and nVidia are dominating (different parts of) the market; Marvell and Microchip are fighting for the scraps. The only "cool" player is Microchip, who have been providing full datasheets, register maps, and open sourcing their drivers for years now. But I'm under no illusions they're doing this out of the goodness of their heart…
Nokia use Broadcom silicon for low-end, in-house for the rest.
Re: Intel's Tofino P4 Software Is Now Open Source
#55I’m impressed by the political acumen it takes to get a Corp to release code as OSS. My career has seen at least two chunks of work that would have made great OSS (ie potentially useful outside of the single company) but Incoukd not get past the final hurdle And they would have been nice CV boosters as well (my real motivation!)
Well. It looks like abandonning software to the community. From the "P4 workflow" described at https://p4.org/ I see mentions of compiling to x86, but no mention of ARM, and no mention of BPF. So, as someone who discover it, I wonder if this project is still relevant in 2025.
Re: Intel's Tofino P4 Software Is Now Open Source
#56does anyone know if someone can make this switchdev friendly?
Re: Intel's Tofino P4 Software Is Now Open Source
#57Earlier quoted context omitted.
ehh scream SDN 5 times. kinda miss the 2010’s now. cisco silicon one uses p4 fwiw. internal development though, but the language makes sense for what the things are.
do they expose the p4 functionality externally? ive heard this from them but never actually seen the proof - it seems like vaporware
Re: Intel's Tofino P4 Software Is Now Open Source
#58Unless there are devices that I could buy (48 port 1U style switches) and until this supports integrating with something like switchdev ( https://docs.kernel.org/networking/switchdev.html ) then this is too little too late. I hope I'm wrong though. does anyone know if someone can make this switchdev friendly?
Writing a switchdev driver is an enormous amount of work so it only happens when someone (usually the chip vendor) pays for it. Any code open-sourced by Intel probably won't meet Linux kernel standards so it would have to be completely rewritten (like the tg3 driver from the old days).
Re: Intel's Tofino P4 Software Is Now Open Source
#59As far as I can tell, Software Defined Networking (which this is about: "P4 is a domain-specific language for network devices") by now is pretty much a decade-old promise that never materialized. I'd still love to be wrong though! So, let's take the next paragraph: "Before P4, vendors had total control over the functionality supported in the network (...) controlled the rollout of new features (e.g., VXLAN), and roll…
P4 is really only needed in data center networks because slower campus/home networks can usually get away with software processing and their lower prices probably can't support the R&D of a programmable architecture.
Re: Intel's Tofino P4 Software Is Now Open Source
#60Am I mistaken or has Intel pretty much shelved the Tofino switching hardware that supports P4 in the first place? I seem to recall Oxide having to switch suppliers over this?
https://bcantrill.dtrace.org/2024/12/08/why-gelsinger-was-wr...