From: Christian Brauner Date: Fri, 14 Nov 2025 11:47:01 +0000 (+0100) Subject: Merge patch series "enable iomap dio write completions from interrupt context v2" X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5ec58e6acdecb0c2b1707002123883fe1da29a98;p=thirdparty%2Flinux.git Merge patch series "enable iomap dio write completions from interrupt context v2" Christoph Hellwig says: Currently iomap defers all write completions to interrupt context. This was based on my assumption that no one cares about the latency of those to simplify the code vs the old direct-io.c. It turns out someone cared, as Avi reported a lot of context switches with ScyllaDB, which at least in older kernels with workqueue scheduling issues caused really high tail latencies. Fortunately allowing the direct completions is pretty easy with all the other iomap changes we had since. While doing this I've also found dead code which gets removed (patch 1) and an incorrect assumption in zonefs that read completions are called in user context, which it assumes for it's error handling. Fix this by always calling error completions from user context (patch 2). Against the vfs-6.19.iomap branch. * patches from https://patch.msgid.link/20251113170633.1453259-1-hch@lst.de: iomap: invert the polarity of IOMAP_DIO_INLINE_COMP iomap: support write completions from interrupt context iomap: rework REQ_FUA selection iomap: always run error completions in user context fs, iomap: remove IOCB_DIO_CALLER_COMP Link: https://patch.msgid.link/20251113170633.1453259-1-hch@lst.de Signed-off-by: Christian Brauner --- 5ec58e6acdecb0c2b1707002123883fe1da29a98