linux-kernel - Re: [PATCH 0/2] perf stat: add per processor socket count aggregation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 07 Feb 2013 11:31:57 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	linux-kernel@...r.kernel.org, peterz@...radead.org, mingo@...e.hu,
	ak@...ux.intel.com, acme@...hat.com, jolsa@...hat.com,
	namhyung.kim@....com
Subject: Re: [PATCH 0/2] perf stat: add per processor socket count aggregation

Hi Stephane,

On Wed,  6 Feb 2013 15:46:00 +0100, Stephane Eranian wrote:
> This patch adds per-processor socket count aggregation
> for system-wide mode measurements. This is a useful
> mode to detect imbalance between sockets for uniform
> workloads.
>
> To enable this mode, use --aggr-socket in addition
> to -a. (system-wide). This mode can be combined with
> interval printing.
>
> The output includes the socket number and the number
> of online processors on that socket. This is useful
> to gauge the amount of aggregation.
>
>  # ./perf stat -I 1000 -a --aggr-socket -e cycles sleep 2
>  #           time socket cpus             counts events
>       1.000097680 S0        4          5,788,785 cycles
>       2.000379943 S0        4         27,361,546 cycles
>       2.001167808 S0        4            818,275 cycles

Can it be genericized to support arbitrary cpu topology like per-core,
per-numa-node or something?

Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/