Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@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: Thu, 23 Dec 2021 05:23:48 +0100	[thread overview]
Message-ID: <20211223042348.EdEhFbEeGJUzFjYCDssAosjpjuozauHu_M9OlhFL8sA@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: 1087 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/34663#issuecomment-1000033467

Comment:
```
class Stats(DumpableObject):
    members_offsets = [
        ('blkio_delay_total', 40),
        ('swapin_delay_total', 56),
        ('read_bytes', 248),
        ('write_bytes', 256),
        ('cancelled_write_bytes', 264)
    ]

    has_blkio_delay_total = False

    def __init__(self, task_stats_buffer):
        sd = self.__dict__
        for name, offset in Stats.members_offsets:
            data = task_stats_buffer[offset:offset + 8]
            sd[name] = struct.unpack('Q', data)[0]

        # This is a heuristic to detect if CONFIG_TASK_DELAY_ACCT is enabled in
        # the kernel.
        if not Stats.has_blkio_delay_total:
            Stats.has_blkio_delay_total = self.blkio_delay_total != 0
```

It's poking at a lot of things, it's not surprising that the heuristic broke.

https://repo.or.cz/w/iotop.git has some more commits, do you think you could test if the more recent version works fine?

  reply	other threads:[~2021-12-23  4:23 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 [this message]
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
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=20211223042348.EdEhFbEeGJUzFjYCDssAosjpjuozauHu_M9OlhFL8sA@z \
    --to=ericonr@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).