On Mon, Sep 22, 2014 at 10:21 AM, Christian Balzer <chibi at gol.com> wrote: > The linux scheduler usually is quite decent in keeping processes where the > action is, thus you see for example a clear preference of DRBD or KVM vnet > processes to be "near" or on the CPU(s) where the IRQs are. Since you're just mentioning it: DRBD, for one, needs to *tell* the kernel that its sender, receiver and worker threads should be on the same CPU. It has done that for some time now, but you shouldn't assume that this is some kernel magic that DRBD can just use. Not suggesting that you're unaware of this, but the casual reader might be. :) Cheers, Florian
 |