After having used & automated configuration of "traditional" switching/routing devices for years (Cisco , Arista, Juniper), I can't wait for P4 devices to take over
Intel's Tofino P4 Software Is Now Open Source
11–20 of 81 posts
Re: Intel's Tofino P4 Software Is Now Open Source
#12After having used & automated configuration of "traditional" switching/routing devices for years (Cisco , Arista, Juniper), I can't wait for P4 devices to take over
Re: Intel's Tofino P4 Software Is Now Open Source
#13Am 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?
I'm not complaining but it's weird that they're open sourcing the SDK now. Maybe it's to support Mount Evans.
Re: Intel's Tofino P4 Software Is Now Open Source
#14Am 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?
Re: Intel's Tofino P4 Software Is Now Open Source
#15So, 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 rollouts took years"
Anyone has a pointer to any actually available hardware capable of L2 and L3 packet processing where I could have implemented VXLAN in, say, weeks using P4? Again, as far as I can tell, it's all either killed-off-a-long-time-ago, "contact us" vaporware, or exotic 40/100-Gb-only Top-o-Rack gear, and even for those, there is nary an "add to cart" button in sight...
Re: Intel's Tofino P4 Software Is Now Open Source
#16Earlier quoted context omitted.
They spoke on their podcast (I think it was there?) about ditching Tofino for the next generation of the Oxide computer. So it sounds like the current model will always ship with Tofino, but due to no future product development they won't use it again in a new machine. It sounded like they had just secured a replacement for the future but I can't remember who it was.
We've talked about it a bunch, most recently when talking about Intel after Gelsinger.[0] I went into more detail on Intel's total mishandling of Tofino in my blog entry describing why Gelsinger was the wrong choice to lead Intel in 2021.[1] As you might imagine, this move from Intel is something that we at Oxide have advocated for strenuously -- and it is a tremendous tribute to the former Tofino team at Intel that…
Re: Intel's Tofino P4 Software Is Now Open Source
#17And they would have been nice CV boosters as well (my real motivation!)
Re: Intel's Tofino P4 Software Is Now Open Source
#18Earlier quoted context omitted.
They spoke on their podcast (I think it was there?) about ditching Tofino for the next generation of the Oxide computer. So it sounds like the current model will always ship with Tofino, but due to no future product development they won't use it again in a new machine. It sounded like they had just secured a replacement for the future but I can't remember who it was.
We've talked about it a bunch, most recently when talking about Intel after Gelsinger.[0] I went into more detail on Intel's total mishandling of Tofino in my blog entry describing why Gelsinger was the wrong choice to lead Intel in 2021.[1] As you might imagine, this move from Intel is something that we at Oxide have advocated for strenuously -- and it is a tremendous tribute to the former Tofino team at Intel that…
Re: Intel's Tofino P4 Software Is Now Open Source
#19After having used & automated configuration of "traditional" switching/routing devices for years (Cisco , Arista, Juniper), I can't wait for P4 devices to take over
What do you want to use P4 for?
The reality is, you end up with a complex stack with no or homegrown documentation that requires experienced engineers to operate and maintain.
In some environments, that's a perfectly fair trade-off. In most, it isn't.
Re: Intel's Tofino P4 Software Is Now Open Source
#20Nah. 5 years ago this would've been bold. Now it's ridding yourself of the baggage of an almost-dead platform that you're about to make fully dead.
Still appreciate getting the tooling as FOSS rather than just terminating it, but let's not go for delusions here.