2017.07.23 18:09:26 (889155502239875076) from Daniel J. Bernstein, replying to "Colm MacCárthaigh (@colmmacc)" (889154301485957120):
Sure: I've used 40-gigabit Infiniband, and of course it tries hard to avoid poking the CPU. But what exactly do you think the RNG issue is?
2017.07.23 15:48:38 (889120071255240705) from Daniel J. Bernstein:
New blog post "Fast-key-erasure random-number generators": https://blog.cr.yp.to/20170723-random.html An effort to clean up several messes simultaneously.
2017.07.23 17:44:08 (889149135084965888) from "Colm MacCárthaigh (@colmmacc)":
One problem with caching output, i.e. the 736 bytes, is jitter. Having every nth packet/record be inexplicably slower kills :(
2017.07.23 17:57:32 (889152510996426757) from Daniel J. Bernstein, replying to "Colm MacCárthaigh (@colmmacc)" (889149135084965888):
Refilling the buffer is a small fraction of a microsecond on one of your server cores. Linux has vastly larger continual jitter than this.
2017.07.23 18:04:39 (889154301485957120) from "Colm MacCárthaigh (@colmmacc)":
Networks today at 25gbit/sec, 100gbit/sec on the industry horizon. Few use Linux networking for encrypting that. Microbursts & incast a pain