onload VS Time-Appliance-Project

Other than that, I heard there's some 3rd party network libraries that are generally considered lower latency, one of them I believe either redhat uses for one of their systems, or it is sponsored by them: https://github.com/Xilinx-CNS/onload

I mean really you want to be doing some kind of (kernel network bypass with some sort of system programming language like C++ for low latency trading systems like this. Arb trading is usually not worth it unless you have a ton of expertise or some crazy mathematical edge that can offset. Plus you need to be guaranteed to execute the trade you ask for which most average joes don't have.

How about the x2 series from Xilinx?

It comes from solarflare who have a long pedigree of low-latency smartnics. They used to supply Cloudflare, and also supply like 50% of fintechs/financial markets.

You can also just use openonload to accelerate your programs. In this case just doing straight linux socket programming, which can be accelerated without dpdk. Or just use the generic linux driver if necessary.

https://github.com/Xilinx-CNS/onload

Ahki SingHania - Akhi is the engineering manager for the Execution team. He has a background in operating systems and networking. Before working on the Internet Computer, he worked on OpenOnload and Barrelfish.

https://github.com/Xilinx-CNS/onload any good?

It used to be openonload.org which seems to redirect to https://github.com/Xilinx-CNS/onload for the source to onload.

Even just specific projects under that have been impactful. For example the open time server project.

Facebooks Time Card is a good starting point if you want to start looking into how higher end timing devices are built: https://github.com/opencomputeproject/Time-Appliance-Project...

Afaik its not currently available for purchase, so it is more of a diy route. If you want a standalone unit, it probably wouldn't be too big of hassle to ducktape that Time Card to e.g. Raspberry Pi CM4 or similar module with pcie and drive a display (or whatev) that way. Or that FPGA on the Time Card probably has enough spare capacity to do it directly too, for a simplified architecture (and maybe better hard realtime control).

Now you can get/build your own atomic pcie clock for ~$300-2000 for your rack!

Time Card is an open-source solution for PTP-enabled networks that provides the accurate time via GNSS—with a high stability (and holdover) oscillator such as an atomic clock as a backup in the event of GNSS failure. zeroibis recommends it for those who "need to go the full self-hosted NTP route."

On a related note if you need to go the full self hosted NTP route: https://github.com/opencomputeproject/Time-Appliance-Project/tree/master/Time-Card

Really nice of them to release this. However, unless I'm missing something, the HDL for the FPGA on the Time Card is not part of the release. It looks like it uses a proprietary IP core from NetTimeLogic

https://github.com/opencomputeproject/Time-Appliance-Project...

They do include FPGA bit streams, but it's disingenuous to claim a fully open source release.