linux-kernel - Re: [PATCH] Add accumulated call counter for memory allocation profiling

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 for Android: free password hash cracker in your pocket

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

Message-ID: <baku3uqaneue53rr7uixlio4hvfgig4kcox3h45y3ijvigwait@sfsxp2pcftqr>
Date: Sun, 30 Jun 2024 15:52:51 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: David Wang <00107082@....com>, akpm@...ux-foundation.org, 
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add accumulated call counter for memory allocation
 profiling

On Sun, Jun 30, 2024 at 12:33:14PM GMT, Suren Baghdasaryan wrote:
> On Mon, Jun 17, 2024 at 8:33 AM David Wang <00107082@....com> wrote:
> >
> > Accumulated call counter can be used to evaluate rate
> > of memory allocation via delta(counters)/delta(time).
> > This metrics can help analysis performance behaviours,
> > e.g. tuning cache size, etc.
> 
> Sorry for the delay, David.
> IIUC with this counter you can identify the number of allocations ever
> made from a specific code location. Could you please clarify the usage
> a bit more? Is the goal to see which locations are the most active and
> the rate at which allocations are made there? How will that
> information be used?
> I'm a bit cautious here because each counter will take more space and
> use some additional cpu cycles.
> Thanks,
> Suren.

Maybe behind another kconfig option?