From: Mike Galbraith <efault@gmx.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ryan Roberts <ryan.roberts@arm.com>
Subject: RFC [PATCH2] fs/writeback: Mitigate move_expired_inodes() induced service latency
Date: Thu, 31 Oct 2024 11:21:45 +0100 [thread overview]
Message-ID: <ad30ef4edfc22e7f29280fdec763189efddda9d0.camel@gmx.de> (raw)
In-Reply-To: <88ae633aa910c7e320b89e5f4779d472f7cffffb.camel@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]
(was regression: mm: vmscan: - size XL irqoff time increase v6.10+)
Break off queueing of IO after we've been at it for a ms or so and a
preemption is due, to keep writeback latency impact at least reasonable.
The IO we're queueing under spinlock still has to be started under that
same lock.
wakeup_rt tracing caught this function spanning 66ms in a i7-4790 box.
With this patch applied on top of one to mitigate even worse IRQ holdoff
induced hits (78ms) by isolate_lru_folios(), the same trivial load that
leads to this and worse (osc kernel package build + bonnie):
T: 1 ( 6211) P:99 I:1500 C: 639971 Min: 1 Act: 7 Avg: 12 Max: 66696
resulted in this perfectly reasonable max:
T: 0 ( 6078) P:99 I:1000 C:1031230 Min: 1 Act: 7 Avg: 4 Max: 4449
Note: cyclictest -Smp99 is only the messenger. This is not an RT issue,
RT is fingering bad generic behavior.
Signed-off-by: Mike Galbraith <efault@gmx.de>
---
fs/fs-writeback.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -29,6 +29,7 @@
#include <linux/tracepoint.h>
#include <linux/device.h>
#include <linux/memcontrol.h>
+#include <linux/sched/clock.h>
#include "internal.h"
/*
@@ -1424,6 +1425,10 @@ static int move_expired_inodes(struct li
struct inode *inode;
int do_sb_sort = 0;
int moved = 0;
+#ifndef CONFIG_PREEMPT_RT
+ u64 then = local_clock();
+ int iter = 0;
+#endif
while (!list_empty(delaying_queue)) {
inode = wb_inode(delaying_queue->prev);
@@ -1439,6 +1444,19 @@ static int move_expired_inodes(struct li
if (sb && sb != inode->i_sb)
do_sb_sort = 1;
sb = inode->i_sb;
+#ifndef CONFIG_PREEMPT_RT
+ /*
+ * We're under ->list_lock here, and the IO being queued
+ * still has to be started. Stop queueing when we've been
+ * at it for a ms or so and a preemption is due, to keep
+ * latency impact reasonable.
+ */
+ if (iter++ < 100 || !need_resched())
+ continue;
+ if (local_clock() - then > NSEC_PER_MSEC)
+ break;
+ iter = 0;
+#endif
}
/* just one sb in list, splice to dispatch_queue and we're done */
[-- Attachment #2: wakeup_rt-trace-6.12.0.g4236f913-master.gz --]
[-- Type: application/gzip, Size: 967956 bytes --]
next prev parent reply other threads:[~2024-10-31 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 12:03 regression: mm: vmscan: - size XL irqoff time increase v6.10+ Mike Galbraith
2024-10-30 6:30 ` Mike Galbraith
2024-10-31 10:21 ` RFC [PATCH1] mm: vmscan: Limit isolate_lru_folios() IRQ holdoff latency impact Mike Galbraith
2024-10-31 10:21 ` Mike Galbraith [this message]
2024-10-31 10:28 ` RFC [PATCH2] fs/writeback: Mitigate move_expired_inodes() induced service latency Mike Galbraith
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=ad30ef4edfc22e7f29280fdec763189efddda9d0.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan.roberts@arm.com \
/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
all inboxes | Powered by JetHome®