[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190430080910.GI2623@hirez.programming.kicks-ass.net>
Date: Tue, 30 Apr 2019 10:09:10 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Feng Tang <feng.tang@...el.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
Jonathan Corbet <corbet@....net>,
Ingo Molnar <mingo@...nel.org>,
Eric W Biederman <ebiederm@...ssion.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andy Lutomirski <luto@...nel.org>,
Ying Huang <ying.huang@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/3] latencytop lock usage improvement
On Mon, Apr 29, 2019 at 04:03:28PM +0800, Feng Tang wrote:
> Hi All,
>
> latencytop is a very nice tool for tracing system latency hotspots, and
> we heavily use it in our LKP test suites.
What data does latency-top give that perf cannot give you? Ideally we'd
remove latencytop entirely.
Powered by blists - more mailing lists