linux-kernel - Re: SLUB: Support for statistics to help analyze allocator behavior

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]

Message-ID: <47A8C508.6010305@cs.helsinki.fi>
Date:	Tue, 05 Feb 2008 22:20:24 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Christoph Lameter <clameter@....com>
CC:	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: SLUB: Support for statistics to help analyze allocator behavior

Christoph Lameter wrote:
> On Tue, 5 Feb 2008, Pekka J Enberg wrote:
> 
>> Hi Christoph,
>>
>> On Mon, 4 Feb 2008, Christoph Lameter wrote:
>>> The statistics provided here allow the monitoring of allocator behavior
>>> at the cost of some (minimal) loss of performance. Counters are placed in
>>> SLUB's per cpu data structure that is already written to by other code.
>> Looks good but I am wondering if we want to make the statistics per-CPU so 
>> that we can see the kmalloc/kfree ping-pong of, for example, hackbench 
> 
> We could do that.... Any idea how to display that kind of information 
> in a meaningful way. Parameter conventions for slabinfo?

We could just print out one total summary and one summary for each CPU 
(and maybe show % of total allocations/fees. That way you can 
immediately spot if some CPUs are doing more allocations/freeing than 
others.

			Pekka
--
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/