On 12/22/19 7:41 PM, Hillf Danton wrote: > > Reschedule the current IO worker if it is becoming a cpu hog. Might make more sense to put this a bit earlier, to avoid the awkward lock juggle. In theory it shouldn't make a difference if we do it _before_ doing new work, or _after_ doing work. We should only be rescheduling if it's running for quite a while. How about putting it after the flushing of signals instead? -- Jens Axboe
