On Tue, Feb 16, 2021 at 09:29:31AM +, David Howells wrote:
> Is there a better way to do it? The intent is to process the assessment phase
> in the calling thread's context if possible rather than bumping over to a
> worker thread. For synchronous I/O, for example, that's done in the
Christoph Hellwig wrote:
> On Mon, Feb 15, 2021 at 10:46:23PM +, David Howells wrote:
> > The in_softirq() in netfs_rreq_terminated() works fine for the cache being
> > on a normal disk, as the completion handlers may get called in softirq
> > context, but for an NVMe drive, the completion
On 2021-02-16 09:42:30 [+0100], Christoph Hellwig wrote:
> On Mon, Feb 15, 2021 at 10:46:23PM +, David Howells wrote:
> > The in_softirq() in netfs_rreq_terminated() works fine for the cache being
> > on a normal disk, as the completion handlers may get called in softirq
> > context, but for
On Mon, Feb 15, 2021 at 10:46:23PM +, David Howells wrote:
> The in_softirq() in netfs_rreq_terminated() works fine for the cache being
> on a normal disk, as the completion handlers may get called in softirq
> context, but for an NVMe drive, the completion handler may get called in
> IRQ
The in_softirq() in netfs_rreq_terminated() works fine for the cache being
on a normal disk, as the completion handlers may get called in softirq
context, but for an NVMe drive, the completion handler may get called in
IRQ context.
Fix to use in_interrupt() instead of in_softirq() throughout the
5 matches
Mail list logo