[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201028145324.GD2628@hirez.programming.kicks-ass.net>
Date: Wed, 28 Oct 2020 15:53:24 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: mingo@...nel.org, linux-kernel@...r.kernel.org, will@...nel.org,
paulmck@...nel.org, hch@....de, axboe@...nel.dk,
chris@...is-wilson.co.uk, davem@...emloft.net, kuba@...nel.org,
fweisbec@...il.com, oleg@...hat.com, vincent.guittot@...aro.org
Subject: Re: [PATCH v3 5/6] irq_work: Provide irq_work_queue_remote()
On Wed, Oct 28, 2020 at 02:40:46PM +0100, Frederic Weisbecker wrote:
> On Wed, Oct 28, 2020 at 12:07:12PM +0100, Peter Zijlstra wrote:
> > While the traditional irq_work relies on the ability to self-IPI, it
> > makes sense to provide an unconditional irq_work_queue_remote()
> > interface.
>
> We may need a reason as well here.
Rewrote it like so.
---
While the traditional irq_work relies on the ability to self-IPI, the
remote irq_work only requires generic SMP bits and can thus be made
available unconditionally.
Powered by blists - more mailing lists