Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751823AbbH0UoM (ORCPT ); Thu, 27 Aug 2015 16:44:12 -0400 Received: from mail-pa0-f53.google.com ([209.85.220.53]:32881 "EHLO mail-pa0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751276AbbH0UoL (ORCPT ); Thu, 27 Aug 2015 16:44:11 -0400 Date: Thu, 27 Aug 2015 13:44:08 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: =?UTF-8?Q?J=C3=B6rn_Engel?= cc: Michal Hocko , Naoya Horiguchi , Andrew Morton , Mike Kravetz , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Naoya Horiguchi Subject: Re: [PATCH v5 2/2] mm: hugetlb: proc: add HugetlbPages field to /proc/PID/status In-Reply-To: <20150827172351.GA29092@Sligo.logfs.org> Message-ID: References: <1440059182-19798-3-git-send-email-n-horiguchi@ah.jp.nec.com> <20150820110004.GB4632@dhcp22.suse.cz> <20150820233450.GB10807@hori1.linux.bs1.fc.nec.co.jp> <20150821065321.GD23723@dhcp22.suse.cz> <20150821163033.GA4600@Sligo.logfs.org> <20150824085127.GB17078@dhcp22.suse.cz> <20150826063813.GA25196@dhcp22.suse.cz> <20150827064817.GB14367@dhcp22.suse.cz> <20150827172351.GA29092@Sligo.logfs.org> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="397176738-220680865-1440708164=:30543" Content-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2147 Lines: 46 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --397176738-220680865-1440708164=:30543 Content-Type: TEXT/PLAIN; CHARSET=UTF-8 Content-Transfer-Encoding: 8BIT Content-ID: On Thu, 27 Aug 2015, Jörn Engel wrote: > On Thu, Aug 27, 2015 at 08:48:18AM +0200, Michal Hocko wrote: > > Can we go with the single and much simpler cumulative number first and > > only add the break down list if it is _really_ required? We can even > > document that the future version of /proc//status might add an > > additional information to prepare all the parsers to be more careful. > > I don't care much which way we decide. But I find your reasoning a bit > worrying. If someone asks for a by-size breakup of hugepages in a few > years, you might have existing binaries that depend on the _absence_ of > those extra characters on the line. > > Compare: > HugetlbPages: 18432 kB > HugetlbPages: 1069056 kB (1*1048576kB 10*2048kB) > > Once someone has written a script that greps for 'HugetlbPages:.*kB$', > you have lost the option of adding anything else to the line. You have > created yet another ABI compatibility headache today in order to save > 112 lines of code. > This is exactly the concern that I have brought up in this thread. We have no other way to sanely export the breakdown in hugepage size without new fields being added later with the hstate size being embedded in the name itself. I agree with the code as it stands in -mm today and I'm thankful to Naoya that a long-term maintainable API has been established. Respectfully, I have no idea why we are still talking about this and I'm not going to be responding further unless something changes in -mm. --397176738-220680865-1440708164=:30543-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/