I wonder why Fibre Channel isn't used as a replacement for TCP in the datacenter. It is a very robust L3 protocol. It was designed to connect block storage devices to servers while making the OS think they are directly connected. OSs do NOT tolerate dropped data when reading and writing to block devices and so Fibre Channel has a extremely robust Token Bucket algorithm. The algo prevents congestion by allowing receiv…
InfiniBand would make more sense than Fibre Channel
It's time to replace TCP in the datacenter (2023)
141–150 of 160 posts
Re: It's time to replace TCP in the datacenter (2023)
#142I wonder why Fibre Channel isn't used as a replacement for TCP in the datacenter. It is a very robust L3 protocol. It was designed to connect block storage devices to servers while making the OS think they are directly connected. OSs do NOT tolerate dropped data when reading and writing to block devices and so Fibre Channel has a extremely robust Token Bucket algorithm. The algo prevents congestion by allowing receiv…
FC was much more expensive than ethernet, so needed a reason to be used. For block storage it is great, if slower than ethernet.
Re: It's time to replace TCP in the datacenter (2023)
#143I wonder why Fibre Channel isn't used as a replacement for TCP in the datacenter. It is a very robust L3 protocol. It was designed to connect block storage devices to servers while making the OS think they are directly connected. OSs do NOT tolerate dropped data when reading and writing to block devices and so Fibre Channel has a extremely robust Token Bucket algorithm. The algo prevents congestion by allowing receiv…
the question is really: does it have anything vendor-specific, interop-breakers? FC seems to work nicely in a single-vendor stack, or at least among specific sets of big-name vendors. that's OK for the "enterprise" market, where prices are expected to be high, and where some integrator is getting a handsome profit for making sure the vendors match. besides consumer, the original non-enterprise market was HPC, and we…
https://fibrechannel.org/preview-the-new-fibre-channel-speed...
Re: It's time to replace TCP in the datacenter (2023)
#144I wonder why Fibre Channel isn't used as a replacement for TCP in the datacenter. It is a very robust L3 protocol. It was designed to connect block storage devices to servers while making the OS think they are directly connected. OSs do NOT tolerate dropped data when reading and writing to block devices and so Fibre Channel has a extremely robust Token Bucket algorithm. The algo prevents congestion by allowing receiv…
Fibrechannel is far too expensive, you need expensive switches, cables/transceivers and cards in addition to the Ethernet you'll need anyways. And this Fibrechannel hardware is quite limited in what you can do with it, by far not as capable as the usual Ethernet/IP stuff with regards to routing, encryption, tunneling, filtering and what not. Similar things are happening with stuff like Infiniband, it has become far t…
Re: It's time to replace TCP in the datacenter (2023)
#145Earlier quoted context omitted.
Fibrechannel is far too expensive, you need expensive switches, cables/transceivers and cards in addition to the Ethernet you'll need anyways. And this Fibrechannel hardware is quite limited in what you can do with it, by far not as capable as the usual Ethernet/IP stuff with regards to routing, encryption, tunneling, filtering and what not. Similar things are happening with stuff like Infiniband, it has become far t…
Is there a fundamental reason why FC is more expensive than Ethernet?
Re: It's time to replace TCP in the datacenter (2023)
#146This has already been done at scale with HTTP/3 (QUIC), it's just not widely distributed beyond the largest sites & most popular web browsers. gRPC for example is still on multiplexed TCP via HTTP/2, which is "good enough" for many. Though it doesn't really replace TCP, it's just that the predominant requirements have changed (as Ousterhout points out). Bruce Davie has a series of articles on this: https://systemsapp…
Re: It's time to replace TCP in the datacenter (2023)
#147As others have already hit upon, the problem forever lies in standardization of whatever is intended to replace TCP in the data center, or the lack thereof. You’re basically looking for a protocol supported in hardware from endpoint to endpoint, including in firewalls, switches, routers, load balancers, traffic shapers, proxies, etcetera - a very tall order indeed. Then, to add to that very expensive list of criteria…
Re: It's time to replace TCP in the datacenter (2023)
#148Earlier quoted context omitted.
Are you suggesting some protocol layer of Fibre Channel to be used over IP over Ethernet? TCP (in practice) runs on top of (mostly) routed IP networks and network architectures. E.g. a spine/leaf network with BGP. Fibre Channel as I understand it is mostly used in more or less point to point connections? I do see some mention of "Switched Fabric" but is that very common?
Fibre Channel is a routed L3 protocol that can support loop-free multi-path typologies.
Re: It's time to replace TCP in the datacenter (2023)
#149Earlier quoted context omitted.
Is there a fundamental reason why FC is more expensive than Ethernet?
since its entire reason to exist was to effect an artificial market segmentation, I guess the answer is .. yes?
Re: It's time to replace TCP in the datacenter (2023)
#150Earlier quoted context omitted.
Fibre Channel is a routed L3 protocol that can support loop-free multi-path typologies.
I'll admit I'm not familiar with the routing protocols used for Fibre Channel. Is there some equivalent of BGP? How well does it scale? What vendors sell FC switches and what's the cost compared to Ethernet/IP/TCP?