On Fri, 2021-09-17 at 08:59 +0200, Rolf Eike Beer wrote: > > What you need is a _fast_ git server. kernel.org or github.com seem to be too > slow for this if you don't sit somewhere in their datacenter. Use something in > your local network, a Xeon E5 with lot's of RAM and connected with 1GBit/s > Ethernet in my case. Even faster: what's coming across that wire should be a constant (is?), variable is only delivery/consumption jitter. If there's really really a pipe problem lurking, you should also be able to trigger by saving the data once, and just catting it, letting interrupts etc provide jitter. Which stdout is left of '|' in a script shouldn't matter one whit to the interpreter/kernel conversation, they're all the same. That said, if I had a reproducer I was confident pointed to the kernel, I'd try to bisect.. boring as hell, but highly effective. -Mike
