From: Christoph Hellwig <hch@infradead.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
frederic@kernel.org, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: blk-softirq vs smp_call_function_single_async()
Date: Mon, 8 Jun 2020 09:42:54 -0700 [thread overview]
Message-ID: <20200608164254.GA2431@infradead.org> (raw)
In-Reply-To: <20200608164009.GD2531@hirez.programming.kicks-ass.net>
On Mon, Jun 08, 2020 at 06:40:09PM +0200, Peter Zijlstra wrote:
> There isn't one, it was meant to be used with static allocations.
>
> Frederic proposed changing all these to irq_work, and I think I'll go do
> that. First dinner though.
The irq_work API looks reasonable. What are the tradeoffs for
smp_call_single_async vs irq_work?
next prev parent reply other threads:[~2020-06-08 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 11:58 Peter Zijlstra
2020-06-08 15:45 ` Christoph Hellwig
2020-06-08 15:58 ` Peter Zijlstra
2020-06-08 16:33 ` Christoph Hellwig
2020-06-08 16:40 ` Peter Zijlstra
2020-06-08 16:42 ` Christoph Hellwig [this message]
2020-06-09 13:38 ` Peter Zijlstra
2020-06-08 21:34 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200608164254.GA2431@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=frederic@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome