Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 20 Aug 2020 08:20:24 +0200 | From | Christoph Hellwig <> | Subject | Re: [RFC][PATCH v2 08/10] smp,irq_work: Use the new irq_work API |
| |
On Wed, Aug 19, 2020 at 11:50:55AM -0700, Linus Torvalds wrote: > On Wed, Aug 19, 2020 at 12:22 AM <peterz@infradead.org> wrote: > > > > That is, the external serialization comes from the non-atomic > > test-and-set they both have. This works nicely when there is external > > state that already serializes things, but totally comes apart (and > > causes trivial list corruption) when you get it wrong. > > Quite often, there just isn't any *need* for serialization, because > there is only ever one op active.
Yes, that's pretty much the block use case. The request gets completed once, and and the IPI is used to bounce it back to the issuing cpu.
| ![\](/images/icornerr.gif) |