3 ms·
My understanding is that the setup needs to allow them to work on packet routing at those speeds, not just send/receive, to simulate SCION.
by FireBeyond 10mo ago
My understanding is that the setup needs to allow them to work on packet routing at those speeds, not just send/receive, to simulate SCION.
- Youden 10mo agoAh, so they need to hold giant routing tables in memory and do lookups in them or something like that?
- Veserv 10mo agoDoes not look like it [1]. It appears to be a protocol that enumerates your exact path, interface by interface, on every data packet. So you can just blindly forward to the next hop written in the packet itself. By my guess, a competent and efficient implementation should be able to run the routing logic at ~30-100 million packets per second per core. That would be ~300-1,000 Gb/s per core, so you would bottleneck on your memory bandwidth if you have even a single copy. [1] https://www.ietf.org/archive/id/draft-dekater-scion-dataplane-10.html#name-life-of-a-scion-data-packet https://www.ietf.org/archive/id/draft-dekater-scion-dataplan...
- wmf 10mo agoDon't forget checking the MACs.
- AdamJacobMuller 10mo agoIs this some MPLS-like thing?