Linux Documentation
 help / color / mirror / Atom feed
From: Florian Schmidt <florian.schmidt@nutanix.com>
To: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kirill Tkhai <ktkhai@virtuozzo.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Yafang Shao <laoar.shao@gmail.com>
Subject: Re: [PATCH 0/2] trace-vmscan-postprocess: fix parsing and output
Date: Wed, 11 Sep 2019 10:30:28 +0000	[thread overview]
Message-ID: <e1ada037-da07-9513-23fc-9a1f90881b80@nutanix.com> (raw)
In-Reply-To: <20190904204241.y6c335djr3bwm6xo@ca-dmjordan1.us.oracle.com>

Hi Daniel,

On 04/09/2019 21:42, Daniel Jordan wrote:
>> In addition, the tables that are printed by the script were not properly
>> aligned any more, so patch 2 fixes the spacing.
> 
> Nit, not for Pages Scanned.  With your series I get
> 
> Kswapd          Kswapd      Order      Pages     Pages    Pages    Pages
> Instance       Wakeups  Re-wakeup    Scanned    Rclmed  Sync-IO ASync-IO
> kswapd0-175          1          0    253694     253691        3   129896               wake-0=1

Whoops, you're right, I'll fix that in v2.


> I wonder if we shouldn't just get rid of the whole script, it's hard to
> remember to keep in sync with vmscan changes and I can't think of a way to
> remedy that short of having mm regression tests that run this.  But your
> patches are an improvement for now.

That's definitely one possibility. If history has shown that these break 
and aren't properly kept in line, they could go. Alternatively, as 
Yafang suggested, integrating them into the perf test suite might help 
with the issues.

I'll ignore that point for now though and just send a v2 for this patch 
series.

Thanks for the feedback,
Florian

  parent reply	other threads:[~2019-09-11 10:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 11:14 [PATCH 0/2] trace-vmscan-postprocess: fix parsing and output Florian Schmidt
2019-09-03 11:14 ` [PATCH 1/2] trace-vmscan-postprocess: sync with tracepoints updates Florian Schmidt
2019-09-04 20:44   ` Daniel Jordan
2019-09-11 10:32     ` Florian Schmidt
2019-09-03 11:14 ` [PATCH 2/2] trace-vmscan-postprocess: fix output table spacing Florian Schmidt
2019-09-04 20:42 ` [PATCH 0/2] trace-vmscan-postprocess: fix parsing and output Daniel Jordan
2019-09-05  4:32   ` Yafang Shao
2019-09-05 15:27     ` Daniel Jordan
2019-09-11 10:30   ` Florian Schmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-15 17:13 Florian Schmidt

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=e1ada037-da07-9513-23fc-9a1f90881b80@nutanix.com \
    --to=florian.schmidt@nutanix.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=daniel.m.jordan@oracle.com \
    --cc=ktkhai@virtuozzo.com \
    --cc=laoar.shao@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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