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:	Wed, 25 Feb 2015 13:44:26 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Konstantin Khlebnikov <koct9i@...il.com>
Cc:	Michal Hocko <mhocko@...e.cz>,
	Konstantin Khlebnikov <khlebnikov@...dex-team.ru>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: hide per-cpu lists in output of show_mem()

On Tue, 24 Feb 2015 13:03:01 +0400 Konstantin Khlebnikov <koct9i@...il.com> wrote:

> On Mon, Feb 23, 2015 at 5:37 PM, Michal Hocko <mhocko@...e.cz> wrote:
> > On Fri 20-02-15 17:39:42, Konstantin Khlebnikov wrote:
> >> This makes show_mem() much less verbose at huge machines. Instead of
> >> huge and almost useless dump of counters for each per-zone per-cpu
> >> lists this patch prints sum of these counters for each zone (free_pcp)
> >> and size of per-cpu list for current cpu (local_pcp).
> >
> > I like this! I do not remember when I found this information useful
> > while debugging either an allocation failure warning or OOM killer
> > report.
> >
> >> Flag SHOW_MEM_PERCPU_LISTS reverts old verbose mode.
> >
> > Nobody seems to be using this flag so why bother?
> 
> Yes. But this might be important for architectures which has asymmetrical
> memory topology, I've heard about unicorns like that.

Please provide more details about this (why important?  How would it
be used) and I'll add it to the changelog.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ