Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933827AbdC3Qs6 (ORCPT ); Thu, 30 Mar 2017 12:48:58 -0400 Received: from mail-pg0-f45.google.com ([74.125.83.45]:33998 "EHLO mail-pg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932913AbdC3Qs5 (ORCPT ); Thu, 30 Mar 2017 12:48:57 -0400 MIME-Version: 1.0 In-Reply-To: <20170330155123.GA3929@cmpxchg.org> References: <20170317231636.142311-1-timmurray@google.com> <20170330155123.GA3929@cmpxchg.org> From: Shakeel Butt Date: Thu, 30 Mar 2017 09:48:55 -0700 Message-ID: Subject: Re: [RFC 0/1] add support for reclaiming priorities per mem cgroup To: Johannes Weiner Cc: Tim Murray , Michal Hocko , Vladimir Davydov , LKML , cgroups@vger.kernel.org, Linux MM , surenb@google.com, totte@google.com, kernel-team@android.com 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: 631 Lines: 13 > A more useful metric for memory pressure at this point is quantifying > that time you spend thrashing: time the job spends in direct reclaim > and on the flipside time the job waits for recently evicted pages to > come back. Combined, that gives you a good measure of overhead from > memory pressure; putting that in relation to a useful baseline of > meaningful work done gives you a portable scale of how effictively > your job is running. > > I'm working on that right now, hopefully I'll have something useful > soon. Johannes, is the work you are doing only about file pages or will it equally apply to anon pages as well?