Re: [PATCH 2/2] sched: Distangle worker accounting from rq lock

On Mon, Apr 08, 2019 at 12:45:05PM -0700, Tejun Heo wrote: > Hello, > > On Wed, Mar 13, 2019 at 05:55:48PM +0100, Sebastian Andrzej Siewior wrote: > > From: Thomas Gleixner > > > > The worker accounting for CPU bound workers is plugged into the core > > scheduler code and the wakeup code. This i

Re: [PATCH 2/2] sched: Distangle worker accounting from rq lock

On 2019-04-08 12:45:05 [-0700], Tejun Heo wrote: > Hello, Hi, … > This looks good from wq side. Peter, are you okay with routing this > through the wq tree? If you wanna take it through the sched tree, > please feel free to add Thank you. > Acked-by: Tejun Heo > > Thanks. Sebastian

Re: [PATCH 2/2] sched: Distangle worker accounting from rq lock

Hello, On Wed, Mar 13, 2019 at 05:55:48PM +0100, Sebastian Andrzej Siewior wrote: > From: Thomas Gleixner > > The worker accounting for CPU bound workers is plugged into the core > scheduler code and the wakeup code. This is not a hard requirement and > can be avoided by keeping track of the sta

[PATCH 2/2] sched: Distangle worker accounting from rq lock

From: Thomas Gleixner The worker accounting for CPU bound workers is plugged into the core scheduler code and the wakeup code. This is not a hard requirement and can be avoided by keeping track of the state in the workqueue code itself. Keep track of the sleeping state in the worker itself and c