From: Matthew Wilcox <willy@infradead.org>
To: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] I/O completions in softirq context
Date: Mon, 10 May 2021 19:11:35 +0100 [thread overview]
Message-ID: <YJl3V5q/+ovcSzJB@casper.infradead.org> (raw)
We have some reports of the interrupt hangcheck watchdog firing when
completing I/Os that are millions of pages long. While it doesn't
really make sense to construct single I/Os that are that big, it does
flag that even, say, a 16MB writeback I/O is going to spend a lot of time
clearing the writeback bit from pages. With 4kB pages, that's 4096
pages. At 2000 cycles per cache miss (and with just the struct pages
being 256kB of data, they're not in L1 cache any more and probably not
in L2 either), that's 8 million cycles with interrupts disabled.
If we could guarantee that BIOs were always ended in softirq context,
the page cache could use spin_lock_bh() instead of spin_lock_irq().
I haven't done any measurements to quantify what kind of improvement
that would be, but I suspect it could be seen on some workloads.
(this is more of an attempt to induce conference driven development
than necessarily a discussion topic for lsfmm)
reply other threads:[~2021-05-10 18:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YJl3V5q/+ovcSzJB@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).