3 ms·
I have found limited success dictating to hardware manufacturers. I would be satisfied if the kernel could just be persuaded to leave my cores the hell alone wi
by ncmncm 6y ago
I have found limited success dictating to hardware manufacturers. I would be satisfied if the kernel could just be persuaded to leave my cores the hell alone without an endless list of boot flags.
- LunaSea 6y agoDo you have links about the flags that you mention or were you referring to process pining? Have you tried out the new eBPF libraries and kTLS?
- ncmncm 6y agoSearch isolcpus, nohz_full, and rcu_nocbs. Process pinning & isolation from other processes is the first step; keeping kernel interruptions out is the hard part. Kernel people generally think anything they do is implicitly more important than every single thing you do. eBPF and kTLS tend to involve the kernel in your business. But, eBPF can put code directly on certain NICs (e.g. Netronome), writing directly to user process memory. Then there is no need to pin or isolate, because the action is on the NIC, out of reach.
- lifty 6y agoAnd then some server vendors insist on on doing some out of bound interrupts from their management engines, which introduce odd latency spikes that are hard to debug.