From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751553AbbJBWiA (ORCPT ); Fri, 2 Oct 2015 18:38:00 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:37530 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751417AbbJBWhR (ORCPT ); Fri, 2 Oct 2015 18:37:17 -0400 Date: Fri, 2 Oct 2015 15:37:16 -0700 From: Andrew Morton To: Vlastimil Babka Cc: linux-mm@kvack.org, Jerome Marchand , Hugh Dickins , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Michal Hocko , "Kirill A. Shutemov" , Cyrill Gorcunov , Randy Dunlap , linux-s390@vger.kernel.org, Martin Schwidefsky , Heiko Carstens , Peter Zijlstra , Paul Mackerras , Arnaldo Carvalho de Melo , Oleg Nesterov , Linux API , Konstantin Khlebnikov Subject: Re: [PATCH v4 3/4] mm, shmem: Add shmem resident memory accounting Message-Id: <20151002153716.8dfc261ed775c63caea92c69@linux-foundation.org> In-Reply-To: <1443792951-13944-4-git-send-email-vbabka@suse.cz> References: <1443792951-13944-1-git-send-email-vbabka@suse.cz> <1443792951-13944-4-git-send-email-vbabka@suse.cz> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2 Oct 2015 15:35:50 +0200 Vlastimil Babka wrote: > From: Jerome Marchand Changelog is a bit weird. > Currently looking at /proc//status or statm, there is no way to > distinguish shmem pages from pages mapped to a regular file (shmem > pages are mapped to /dev/zero), even though their implication in > actual memory use is quite different. OK, that's a bunch of stuff about the user interface. > This patch adds MM_SHMEMPAGES counter to mm_rss_stat to account for > shmem pages instead of MM_FILEPAGES. And that has nothing to do with the user interface. So now this little reader is all confused. The patch doesn't actually address the described problem at all, does it? It's preparatory stuff only? No changes to the kernel's user interface?