From: kipade <kipade@163.com>
To: kernelnewbies@kernelnewbies.org
Subject: why high io requests will slow down kernel scheduling?
Date: Sat, 16 Dec 2023 20:52:58 +0800 (CST) [thread overview]
Message-ID: <b228a8f.13a2.18c72afe1a0.Coremail.kipade@163.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 516 bytes --]
Hello, Im puzzled about the influence about iowait. Almost all the document say, the iowait "Show the percentage of time that the CPU or CPUs were idle during which the system had an outstanding disk I/O request."
And, if there was a programs writing disk frequently, the system's iowait would be very high and the cpu was very free(do nothing). If so, the kernel's process scheduling should work fine, but the process scheduling lantency was very high(some programs were rescheduled after a long time). Why? Thanks
[-- Attachment #1.2: Type: text/html, Size: 1262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2023-12-16 12:55 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=b228a8f.13a2.18c72afe1a0.Coremail.kipade@163.com \
--to=kipade@163.com \
--cc=kernelnewbies@kernelnewbies.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