linux-kernel - Re: [RFC/PATCHSET 0/6] perf kmem: Implement page allocation analysis (v1)

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:	Fri, 13 Mar 2015 13:44:20 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Jiri Olsa <jolsa@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	David Ahern <dsahern@...il.com>,
	Minchan Kim <minchan@...nel.org>,
	Joonsoo Kim <js1304@...il.com>
Subject: Re: [RFC/PATCHSET 0/6] perf kmem: Implement page allocation analysis
 (v1)


* Namhyung Kim <namhyung@...nel.org> wrote:

> Hi Ingo,
> 
> On Thu, Mar 12, 2015 at 04:54:22PM +0100, Ingo Molnar wrote:
> > 
> > * Namhyung Kim <namhyung@...nel.org> wrote:
> > 
> > > > I.e. something like this (mockup) output:
> > > > 
> > > >    SUMMARY (page allocator)
> > > >    ========================
> > > > 
> > > >    Pages allocated+freed:       12,593   [     51,630,080 bytes ]
> > > > 
> > > >    Pages allocated-only:         2,342   [      1,235,010 bytes ]
> > > >    Pages freed-only:                67   [        135,311 bytes ]
> > > > 
> > > >    Page allocation failures :        0
> > > 
> > > Looks a lot better!
> > > 
> > > One thing I need to tell you is that the numbers are not pages but 
> > > requests.
> > 
> > Yes, but in the MM code we tend to call larger order allocations 
> > 'pages' as well: higher order pages, such as a 2MB hugepage, or a 8K 
> > order-1 page. So at least in MM-speak it should be OK to call them 
> > 'pages'.
> > 
> > But your call!
> 
> How about this?
> 
>   SUMMARY (page allocator)
>   ========================
>   Total allocation requests   :        9,015  [     37,200 Kbytes ]  (A)
>   Total free requests         :        8,093  [     33,176 Kbytes ]  (B)
> 
>   Total alloc+freed requests  :        7,985  [     32,732 Kbytes ]  (C)
>   Total alloc-only requests   :        1,030  [      4,468 Kbytes ]  (D)
>   Total free-only requests    :          108  [        444 Kbytes ]  (E)
> 
>   Total allocation failure    :            0  [          0 Kbytes ]

s/failure/failures
s/Kbytes/KB

I'd leave a bit more space for the numbers, for up into billions of 
requests and terabytes of data. Other than that, sounds good to me!

Thanks,

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