From: bbonev <bbonev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: iotop complains "CONFIG_TASK_DELAY_ACCT not enabled in kernel", but it is
Date: Sun, 09 Jan 2022 22:36:02 +0100 [thread overview]
Message-ID: <20220109213602.4FqCKs53Lrg-CK1wJC6YzC08p_eF59awQ8MCtzAwOYQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34663@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
New comment by bbonev on void-packages repository
https://github.com/void-linux/void-packages/issues/34663#issuecomment-1008428531
Comment:
> They had the issue and solved it: [Tomas-M/iotop#21](https://github.com/Tomas-M/iotop/issues/21)
>
> Apparently `iotop` needs `kernel.task_delayacct` to be enabled, however since kernel 5.15 it seems to be disabled https://www.kernel.org/doc/html/v5.15/accounting/delay-accounting.html
The above link points to the C rewrite of `iotop` (packaged as `iotop-c` in many Linux distributions but not in Void Linux) while the python one is located at https://repo.or.cz/iotop.git; the OP obviously talks about the python version of `iotop`.
The fix mentioned above is for the C version where the user can toggle the `task_delayacct` sysctl with a shortcut. The python version only gives a warning in case the sysctl is off and SWAPIN/IO do not work (the fix is not in a released version yet, one option is to package the HEAD of the python iotop's repo).
Hope I could reduce the confusion...
next prev parent reply other threads:[~2022-01-09 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 11:42 [ISSUE] " Mek101
2021-12-23 4:23 ` ericonr
2021-12-23 9:31 ` Mek101
2021-12-23 14:17 ` ericonr
2021-12-23 21:27 ` Mek101
2021-12-23 21:28 ` Mek101
2021-12-23 21:33 ` Mek101
2021-12-23 21:35 ` Mek101
2021-12-29 18:07 ` Mek101
2022-01-09 21:36 ` bbonev [this message]
2022-06-20 2:13 ` github-actions
2022-07-04 2:15 ` [ISSUE] [CLOSED] " github-actions
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=20220109213602.4FqCKs53Lrg-CK1wJC6YzC08p_eF59awQ8MCtzAwOYQ@z \
--to=bbonev@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).