Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757756AbbEWIW3 (ORCPT ); Sat, 23 May 2015 04:22:29 -0400 Received: from mail-wg0-f51.google.com ([74.125.82.51]:34313 "EHLO mail-wg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756751AbbEWIWZ (ORCPT ); Sat, 23 May 2015 04:22:25 -0400 Date: Sat, 23 May 2015 10:22:21 +0200 From: Ingo Molnar To: Josef Bacik Cc: a.p.zijlstra@chello.nl, mingo@redhat.com, acme@kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com Subject: Re: [PATCH V2] perf-sched: add option to merge like comms to lat output Message-ID: <20150523082221.GA7025@gmail.com> References: <1432300720-30478-1-git-send-email-jbacik@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1432300720-30478-1-git-send-email-jbacik@fb.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2295 Lines: 38 * Josef Bacik wrote: > Sometimes when debugging large multi-threaded applications it is helpful to > collate all of the latency numbers into one bulk record to get an idea of what > is going on. This patch does this by merging any entries that belong to the > same comm into one entry and then spits out those totals. I've also slightly > changed the output so you can see how many threads were merged in the > processing. Here is the new default output format > > ----------------------------------------------------------------------------------------------------------------- > Task | Runtime ms | Switches | Average delay ms | Maximum delay ms | Maximum delay at | > ----------------------------------------------------------------------------------------------------------------- > chrome:(23) | 740.878 ms | 2612 | avg: 0.022 ms | max: 0.845 ms | max at: 7935.254223 s > pulseaudio:1523 | 94.440 ms | 597 | avg: 0.027 ms | max: 0.110 ms | max at: 7934.668372 s > threaded-ml:6042 | 72.554 ms | 386 | avg: 0.035 ms | max: 1.186 ms | max at: 7935.330911 s > Chrome_IOThread:3832 | 52.388 ms | 456 | avg: 0.021 ms | max: 1.365 ms | max at: 7935.330602 s > Chrome_ChildIOT:(7) | 50.694 ms | 743 | avg: 0.021 ms | max: 1.448 ms | max at: 7935.256659 s > Compositor:5510 | 30.012 ms | 192 | avg: 0.019 ms | max: 0.131 ms | max at: 7936.636815 s > plugin_audio_th:6043 | 24.828 ms | 314 | avg: 0.018 ms | max: 0.143 ms | max at: 7936.205994 s > CompositorTileW:(2) | 14.099 ms | 45 | avg: 0.022 ms | max: 0.153 ms | max at: 7937.521800 s > > the (#) after the task is the number of tasks merged, and then if > there were no tasks merged it just shows the pid. Here is the same > trace file with the -p option to print the per-pid latency numbers Nice! Acked-by: Ingo Molnar Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/