All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: 5.14-rc breaks iotop swap io monitoring.
Date: Tue, 24 Aug 2021 20:29:08 -0400	[thread overview]
Message-ID: <20210825002908.GA16064@codemonkey.org.uk> (raw)
In-Reply-To: <CAHk-=wg8XonsSN1SXjpSh3pO3-+EMZvdkb1xwJbLpZxCT2=thQ@mail.gmail.com>

On Tue, Aug 24, 2021 at 04:26:59PM -0700, Linus Torvalds wrote:
 > >  > What happens if you boot with the 'delayacct' kernel parameter.
 > >  >
 > > Yeah that boot option does make iotop work again.
 > 
 > Ok, so it's that delay allocation thing is it.
 > 
 > I'm inclined to let it be and see if somebody else notices, and how
 > big of a deal it is.
 >
 > The 'delayacct' kernel command line is an acceptable workaround if
 > this is something only a few people will even notice or care about.
 > 
 > I wonder how much people care about some statistics and iotop these days.
 > 
 > I also assume the swap stats still show up in "vmstat" etc, and that
 > it's just that iotop ended up using fancier interfaces?

afaict, vmstat is fine (though none of my machines are using swap, so
they're just reporting 0)

	Dave


  reply	other threads:[~2021-08-25  0:29 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
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 [this message]
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=20210825002908.GA16064@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.