Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753713AbbERJ4u (ORCPT ); Mon, 18 May 2015 05:56:50 -0400 Received: from mail-pd0-f179.google.com ([209.85.192.179]:34176 "EHLO mail-pd0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753604AbbERJ43 (ORCPT ); Mon, 18 May 2015 05:56:29 -0400 Date: Mon, 18 May 2015 18:56:49 +0900 From: Sergey Senozhatsky To: Karel Zak Cc: Sergey Senozhatsky , Minchan Kim , Sergey Senozhatsky , linux-kernel@vger.kernel.org, util-linux@vger.kernel.org Subject: Re: what's cooking in zram for 4.1 Message-ID: <20150518095649.GB2330@swordfish> References: <20150509042148.GA514@swordfish> <20150518093645.GL4834@ws.net.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150518093645.GL4834@ws.net.home> 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 Content-Length: 1157 Lines: 34 On (05/18/15 11:36), Karel Zak wrote: > On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: > > There will be some user-space visible changes in zram 4.1 we'd love to let you know > > about. > > ... > > > -- /sys/block/zram/mm_stat > > > > The stat file represents device's mm statistics. It consists of a single > > line of text and contains the following stats separated by whitespace: > > orig_data_size > > compr_data_size > > mem_used_total > > mem_limit > > mem_used_max > > zero_pages > > num_migrated > > OK, zramctl(8) code in util-linux git tree supports mm_stat file now. > It's able to fallback to the original /sys/block/zram/ if > mm_stat does not exist. The change will be available in v2.27 (~Aug 2015). > > I have also added support for MEM-LIMIT, MEM-USED and MIGRATED columns. > great, thanks! -ss -- 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/