Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932111AbbFGGL2 (ORCPT ); Sun, 7 Jun 2015 02:11:28 -0400 Received: from mail-wi0-f169.google.com ([209.85.212.169]:36965 "EHLO mail-wi0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750846AbbFGGLR (ORCPT ); Sun, 7 Jun 2015 02:11:17 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 7 Jun 2015 11:41:15 +0530 X-Google-Sender-Auth: Y7mPzyfYsPWMDdTgmY-Z0jjmCBk Message-ID: Subject: Re: [PATCH v5 0/4] idle memory tracking From: Raghavendra KT To: Vladimir Davydov Cc: Andrew Morton , Minchan Kim , Johannes Weiner , Michal Hocko , Greg Thelen , Michel Lespinasse , David Rientjes , Pavel Emelyanov , Cyrill Gorcunov , Jonathan Corbet , linux-api@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, Linux Kernel Mailing List , Raghavendra KT Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1513 Lines: 33 On Tue, May 12, 2015 at 7:04 PM, Vladimir Davydov wrote: > Hi, > > This patch set introduces a new user API for tracking user memory pages > that have not been used for a given period of time. The purpose of this > is to provide the userspace with the means of tracking a workload's > working set, i.e. the set of pages that are actively used by the > workload. Knowing the working set size can be useful for partitioning > the system more efficiently, e.g. by tuning memory cgroup limits > appropriately, or for job placement within a compute cluster. > > ---- USE CASES ---- > > The unified cgroup hierarchy has memory.low and memory.high knobs, which > are defined as the low and high boundaries for the workload working set > size. However, the working set size of a workload may be unknown or > change in time. With this patch set, one can periodically estimate the > amount of memory unused by each cgroup and tune their memory.low and > memory.high parameters accordingly, therefore optimizing the overall > memory utilization. > Hi Vladimir, Thanks for the patches, I was able test how the series is helpful to determine docker container workingset / idlemem with these patches. (tested on ppc64le after porting to a distro kernel). -- 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/