On Tue, 7 Dec 2021 at 11:42, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > On Tue, Dec 07, 2021 at 11:20:59AM +0100, Miklos Szeredi wrote: > > That may be good for fuse as the data is indeed shared. It would be > > even better if the woken task had already a known affinity to this > > CPU, since that would mean thread local data wouldn't have to be > > migrated each time... So I'm not sure sync wakeup alone is worth it, > > needs real life benchmarking. > > Hard affinities have other down-sides.. occasional migrations shouldn't > be a problem, constant migrations are bad. Currently fuse readers are sleeping in wait_event_interruptible_exclusive(). wake_up_interruptible_sync() will pick the first thread in the queue and wake that up. That will likely result in migration, right? What would be much nicer, is to look at all the threads on the waitq and pick one that previously ran on the current CPU if there's one. Could this be implemented? Thanks, Miklos
