From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932314AbbCLPJm (ORCPT ); Thu, 12 Mar 2015 11:09:42 -0400 Received: from mail-qg0-f43.google.com ([209.85.192.43]:37079 "EHLO mail-qg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932237AbbCLPJl (ORCPT ); Thu, 12 Mar 2015 11:09:41 -0400 Date: Thu, 12 Mar 2015 11:09:37 -0400 From: Michal Hocko To: Marcos Dione Cc: linux-kernel@vger.kernel.org, marcos-david.dione@amadeus.com, linux-mm@kvack.org Subject: Re: committed memory, mmaps and shms Message-ID: <20150312150937.GA13256@dhcp22.suse.cz> References: <20150311181044.GC14481@diablo.grulicueva.local> <20150312124053.GA30035@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150312124053.GA30035@dhcp22.suse.cz> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 12-03-15 08:40:53, Michal Hocko wrote: [...] > I think it would make more sense to add something like easily > reclaimable chache to the output of free (pagecache-shmem-dirty > basically). That would give an admin a better view on immediatelly > re-usable memory. Ohh, I have just learned that /proc/meminfo already provides such an information. It's MemAvailable and should give you an idea about how much memory is re-usable. -- Michal Hocko SUSE Labs