From: Dave Jones <davej@codemonkey.org.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 5.14-rc breaks iotop swap io monitoring.
Date: Tue, 24 Aug 2021 11:19:43 -0400 [thread overview]
Message-ID: <20210824151943.GA386@codemonkey.org.uk> (raw)
In-Reply-To: <YSSuVO47ieWDfWMQ@hirez.programming.kicks-ass.net>
On Tue, Aug 24, 2021 at 10:31:16AM +0200, Peter Zijlstra wrote:
> On Mon, Aug 23, 2021 at 11:16:48PM -0400, Dave Jones wrote:
> > I just noticed that in 5.14-rc running iotop, it complains on startup
> > that "CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine
> > SWAPIN and IO %" and sure enough a bunch of columns show up as
> > 'unavailable'.
> >
> > My suspicion is this commit, which I've not confirmed yet as it doesn't
> > cleanly revert. I'll poke at it some more in the morning, but figured
> > I'd bring it up sans-evidence in the hope that I'll wake up to someone
> > having an Ah-ha moment.
>
> If you need DELAYACCT I'm thinking:
>
> e4042ad49235 ("delayacct: Default disabled")
>
> and
>
> 0cd7c741f01d ("delayacct: Add sysctl to enable at runtime")
That does sound more relevant. however, even after echo 1 > /proc/sys/kernel/task_delayacct,
it still fails in the same way.
Dave
next prev parent reply other threads:[~2021-08-24 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 3:16 5.14-rc breaks iotop swap io monitoring Dave Jones
2021-08-24 3:18 ` Dave Jones
2021-08-24 8:31 ` Peter Zijlstra
2021-08-24 15:19 ` Dave Jones [this message]
2021-08-24 16:34 ` Linus Torvalds
2021-08-24 17:35 ` Peter Zijlstra
2021-08-24 21:33 ` Dave Jones
2021-08-24 23:26 ` Linus Torvalds
2021-08-25 0:29 ` Dave Jones
2021-08-25 7:36 ` Peter Zijlstra
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=20210824151943.GA386@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@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