From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751966AbcFCIBt (ORCPT ); Fri, 3 Jun 2016 04:01:49 -0400 Received: from mail-pa0-f67.google.com ([209.85.220.67]:36377 "EHLO mail-pa0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750816AbcFCIBs (ORCPT ); Fri, 3 Jun 2016 04:01:48 -0400 Date: Fri, 3 Jun 2016 17:01:41 +0900 From: Sergey Senozhatsky To: Minchan Kim Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Sangseok Lee , Chanho Min , Chan Gyun Jeong Subject: Re: [PATCH] mm: add NR_ZSMALLOC to vmstat Message-ID: <20160603080141.GA490@swordfish> References: <1464919731-13255-1-git-send-email-minchan@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1464919731-13255-1-git-send-email-minchan@kernel.org> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (06/03/16 11:08), Minchan Kim wrote: > Now, zram is very popular for some of embedded world(e.g., TV, mobile > phone). On those system, zsmalloc consumed memory size is never trivial > (one of example from real product system, total memory: 800M, zsmalloc > consumed: 150M), so we have used this out of tree patch to monitor system > memory behavior via /proc/vmstat. > > With zsmalloc in vmstat, it helps tracking down system behavior by > memory usage. Hello, may be use zsmalloc stats file instead? as far as I know, you keep zsmalloc stats enabled in production anyway. -ss