| 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
| ||
|
Message-ID: <alpine.DEB.2.02.1303201157120.17761@chino.kir.corp.google.com> Date: Wed, 20 Mar 2013 11:58:20 -0700 (PDT) From: David Rientjes <rientjes@...gle.com> To: Michal Hocko <mhocko@...e.cz> cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [patch] mm, hugetlb: include hugepages in meminfo On Wed, 20 Mar 2013, Michal Hocko wrote: > > I didn't do this because it isn't already exported in /proc/meminfo and > > since we've made an effort to reduce the amount of information emitted by > > the oom killer at oom kill time to avoid spamming the kernel log, I only > > print the default hstate. > > I do not see how this would make the output too much excessive. If > you do not want to have too many lines in the output then the hstate > loop can be pushed inside the node loop and have only per-node number > of lines same as you are proposing except you would have a complete > information. > Besides that we are talking about handful of hstates. > Sigh. Because nobody is going to be mapping non-default hstates and then not know about them at oom time; 1GB hugepages on x86 with pse must be reserved at boot and never freed, for example. I'll add them but it's just a waste of time. -- 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