From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com [209.85.167.71]) by kanga.kvack.org (Postfix) with ESMTP id B8DDB8E0001 for ; Mon, 17 Sep 2018 09:29:50 -0400 (EDT) Received: by mail-lf1-f71.google.com with SMTP id h4-v6so910266lfc.22 for ; Mon, 17 Sep 2018 06:29:50 -0700 (PDT) Received: from SELDSEGREL01.sonyericsson.com (seldsegrel01.sonyericsson.com. [37.139.156.29]) by mx.google.com with ESMTPS id o21-v6si10461565lff.74.2018.09.17.06.29.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Sep 2018 06:29:49 -0700 (PDT) Subject: Re: [PATCH 0/9] psi: pressure stall information for CPU, memory, and IO v4 References: <20180828172258.3185-1-hannes@cmpxchg.org> <20180905214303.GA30178@cmpxchg.org> <20180907110407.GQ24106@hirez.programming.kicks-ass.net> <20180907150955.GC11088@cmpxchg.org> From: peter enderborg Message-ID: <29f0bb2c-31d4-0b2e-d816-68076b90e9d3@sony.com> Date: Mon, 17 Sep 2018 15:29:41 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Language: en-GB Sender: owner-linux-mm@kvack.org List-ID: To: Suren Baghdasaryan , Johannes Weiner Cc: Peter Zijlstra , Ingo Molnar , Andrew Morton , Linus Torvalds , Tejun Heo , Daniel Drake , Vinayak Menon , Christopher Lameter , Shakeel Butt , Mike Galbraith , linux-mm , cgroups@vger.kernel.org, LKML , kernel-team@fb.com Will it be part of the backport to 4.9 google android or is it for test only? I guess that this patch is to big for the LTS tree. On 09/07/2018 05:58 PM, Suren Baghdasaryan wrote: > Thanks for the new patchset! Backported to 4.9 and retested on ARMv8 8 > code system running Android. Signals behave as expected reacting to > memory pressure, no jumps in "total" counters that would indicate an > overflow/underflow issues. Nicely done! > > Tested-by: Suren Baghdasaryan > > On Fri, Sep 7, 2018 at 8:09 AM, Johannes Weiner wrote: >> On Fri, Sep 07, 2018 at 01:04:07PM +0200, Peter Zijlstra wrote: >>> So yeah, grudingly acked. Did you want me to pick this up through the >>> scheduler tree since most of this lives there? >> Thanks for the ack. >> >> As for routing it, I'll leave that decision to you and Andrew. It >> touches stuff all over, so it could result in quite a few conflicts >> between trees (although I don't expect any of them to be non-trivial).