[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190905152710.4gndiwcqcgkp4zcq@ca-dmjordan1.us.oracle.com>
Date: Thu, 5 Sep 2019 11:27:10 -0400
From: Daniel Jordan <daniel.m.jordan@...cle.com>
To: Yafang Shao <laoar.shao@...il.com>
Cc: Daniel Jordan <daniel.m.jordan@...cle.com>,
Florian Schmidt <florian.schmidt@...anix.com>,
Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>,
Kirill Tkhai <ktkhai@...tuozzo.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] trace-vmscan-postprocess: fix parsing and output
On Thu, Sep 05, 2019 at 12:32:49PM +0800, Yafang Shao wrote:
> On Thu, Sep 5, 2019 at 4:42 AM Daniel Jordan <daniel.m.jordan@...cle.com> wrote:
> > 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.
>
> There are some similar scripts under tools/perf/scripts/, i.e.
> compaction-times.py.
> What about intergrating these vmscan scripts into perf/scripts as well ?
> Something like vmscan-times.py...
Could be done, but I don't see how that makes it easier to keep in
sync...unless perf's tests are run regularly.
Powered by blists - more mailing lists