Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4797818imm; Mon, 14 May 2018 13:17:56 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpFR1QpX0mB+HruhAy5TsSl5nDvXYbhIaGhlc0fhqFEeUVTqyd9OSb83/9iG4a91ufJfNpt X-Received: by 2002:a65:4309:: with SMTP id j9-v6mr9510678pgq.375.1526329076723; Mon, 14 May 2018 13:17:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526329076; cv=none; d=google.com; s=arc-20160816; b=PJyk7m9AtlRt21Lewpyg0BuGPlHilwJV2zuJkRNnwwLe6x2KfJ0Q/vHxZQQQ7Q3nWa DrnzUqKDPjygOrDbaHqWIyAIyOx6GEcBSVi9kIKK6LeucNh8UyIcpTwEwD+b4XtdXC68 u+6Ro6XXr5+ZEzY+lWJ6Gp5x5XdAdp/lwGFlQkOSEyjXDwuG90Uqfq1KwdjrE65YXVOm FkyJFm7IJgDus7iocjSA/6246DsjngnMNphs15GUEF+X1uaaAr9YhOCk5TiOpDwEPlRo Eq/Tp2v1j8Se5Ygg5KlzCCI7XXS7A8gmXx8IJlkL8dN1Vx9fmLEf7TYIMKe5u3c09PnA /H7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:feedback-id:mime-version:user-agent :references:message-id:in-reply-to:subject:cc:to:from:date :dkim-signature:arc-authentication-results; bh=Q8qPqzBa5m7L/sRi/d6xL7H4RD0c77gF8yCVTDEi6rk=; b=Pz1LJ95GtJP5E9UtZVoq7pwNw6RLLR+tHBohQ/ITI/67tRpyOFffJZMjvg+QomvxTs Go/5uXHrWz4xEuTgAKWpPSezE+A1ve5cJl6R8A1QQEfWiVgPsB/7+jORLKnMSUBLBJCj W/AEutfr4Kd2WSrYQn3rkCtTNn31wbnOLW//U5pS8/30vOq+Vdu/CBZPieCfzytWV20F q+yzz3qyHNrUBcp7M4dyickRrktKJ550pmb0+IRxgAgYeHhh2LoqvlPjLw2lBCXPye7a cpbUUtqR9E/vVUB5esDui75okD8kZFrerjG23QHMLpQBlB+93EBCLOoLVDkZkAMDyfpF YAtA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amazonses.com header.s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug header.b=HxsLc3w8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f21-v6si6265343pgv.382.2018.05.14.13.17.42; Mon, 14 May 2018 13:17:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@amazonses.com header.s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug header.b=HxsLc3w8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752115AbeENUPw (ORCPT + 99 others); Mon, 14 May 2018 16:15:52 -0400 Received: from a9-54.smtp-out.amazonses.com ([54.240.9.54]:36582 "EHLO a9-54.smtp-out.amazonses.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751865AbeENUPv (ORCPT ); Mon, 14 May 2018 16:15:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1526328950; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:MIME-Version:Content-Type:Feedback-ID; bh=Q8qPqzBa5m7L/sRi/d6xL7H4RD0c77gF8yCVTDEi6rk=; b=HxsLc3w88slSx0f4GXVHXAgrxm6md9d1u9vuvLsucwQX3+2ngehU0q74ZtQX+y5e uiLWKg49n0EAZtwjAIPTEI61EFXDBA1teINOz9K/gorb9BekJwGtj1tFDjHpBsPO+lo dx6PuiKr2uJOzbnyT4Mec+SCao2GSuXlcEOxu7ok= Date: Mon, 14 May 2018 20:15:50 +0000 From: Christopher Lameter X-X-Sender: cl@nuc-kabylake To: Johannes Weiner cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-block@vger.kernel.org, cgroups@vger.kernel.org, Ingo Molnar , Peter Zijlstra , Andrew Morton , Tejun Heo , Balbir Singh , Mike Galbraith , Oliver Yang , Shakeel Butt , xxx xxx , Taras Kondratiuk , Daniel Walker , Vinayak Menon , Ruslan Ruslichenko , kernel-team@fb.com Subject: Re: [PATCH 0/7] psi: pressure stall information for CPU, memory, and IO In-Reply-To: <20180514185520.GA7398@cmpxchg.org> Message-ID: <01000163604b7e9e-c2729157-aed2-4f5b-bebe-1bf16261ab88-000000@email.amazonses.com> References: <20180507210135.1823-1-hannes@cmpxchg.org> <010001635f4e8be9-94e7be7a-e75c-438c-bffb-5b56301c4c55-000000@email.amazonses.com> <20180514185520.GA7398@cmpxchg.org> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-SES-Outgoing: 2018.05.14-54.240.9.54 Feedback-ID: 1.us-east-1.fQZZZ0Xtj2+TD7V5apTT/NrT6QKuPgzCT/IC7XYgDKI=:AmazonSES Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 14 May 2018, Johannes Weiner wrote: > Since I'm using the same model and infrastructure for memory and IO > load as well, IMO it makes more sense to present them in a coherent > interface instead of trying to retrofit and change the loadavg file, > which might not even be possible. Well I keep looking at the loadavg output from numerous tools and then in my mind I divide by the number of processors, guess if any of the threads would be doing I/O and if I cannot figure that out groan and run "vmstat" for awhile to figure that out. Lets have some numbers there that make more sense please.