Re: [PATCH 5/5] nohz: Use IPI implicit full barrier against rq->nr_running r/w

On Tue, Jun 03, 2014 at 04:40:20PM +0200, Frederic Weisbecker wrote: > A full dynticks CPU is allowed to stop its tick when a single task runs. > Meanwhile when a new task gets enqueued, the CPU must be notified so that > it can restart its tick to maintain local fairness and other accounting > det

[PATCH 5/5] nohz: Use IPI implicit full barrier against rq->nr_running r/w

A full dynticks CPU is allowed to stop its tick when a single task runs. Meanwhile when a new task gets enqueued, the CPU must be notified so that it can restart its tick to maintain local fairness and other accounting details. This notification is performed by way of an IPI. Then when the target

[PATCH 5/5] nohz: Use IPI implicit full barrier against rq->nr_running r/w

A full dynticks CPU is allowed to stop its tick when a single task runs. Meanwhile when a new task gets enqueued, the CPU must be notified so that it can restart its tick to maintain local fairness and other accounting details. This notification is performed by way of an IPI. Then when the target

[PATCH 5/5] nohz: Use IPI implicit full barrier against rq->nr_running r/w

A full dynticks CPU is allowed to stop its tick when a single task runs. Meanwhile when a new task gets enqueued, the CPU must be notified so that it restart its tick to maintain local fairness and other accounting details. This notification is performed by way of an IPI. Then when the target rece

[PATCH 5/5] nohz: Use IPI implicit full barrier against rq->nr_running r/w

A full dynticks CPU is allowed to stop its tick when a single task runs. Meanwhile when a new task gets enqueued, the CPU must be notified so that it restart its tick to maintain local fairness and other accounting details. This notification is performed by way of an IPI. Then when the target rece