Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031624AbbD2H7K (ORCPT ); Wed, 29 Apr 2015 03:59:10 -0400 Received: from mx2.parallels.com ([199.115.105.18]:59442 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031044AbbD2H7H (ORCPT ); Wed, 29 Apr 2015 03:59:07 -0400 Date: Wed, 29 Apr 2015 10:58:53 +0300 From: Vladimir Davydov To: Minchan Kim CC: Andrew Morton , Johannes Weiner , Michal Hocko , Greg Thelen , Michel Lespinasse , David Rientjes , Pavel Emelyanov , Cyrill Gorcunov , Jonathan Corbet , , , , , Subject: Re: [PATCH v3 0/3] idle memory tracking Message-ID: <20150429075853.GC1694@esperanza> References: <20150429035722.GA11486@blaptop> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20150429035722.GA11486@blaptop> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1033 Lines: 24 Hi Minchan, Thank you for taking a look at this patch set. On Wed, Apr 29, 2015 at 12:57:22PM +0900, Minchan Kim wrote: > On Tue, Apr 28, 2015 at 03:24:39PM +0300, Vladimir Davydov wrote: > > * /proc/kpageidle. For each page this file contains a 64-bit number, which > > equals 1 if the page is idle or 0 otherwise, indexed by PFN. A page is > > Why do we need 64bit per page to indicate just idle or not? I don't think we need this, actually. I made this file 64 bit per page only to conform to other /proc/kpage* files. Currently, I can't think of any potential use for residual 63 bits, so personally I'm fine with 1 bit per page. If nobody comes with an idea about how > 1 bits could be used, I'll switch /proc/kpageidle to a bitmask in the next iteration. Thanks, Vladimir -- 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/