From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-13.6 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 14D4E7D912 for ; Thu, 24 Jan 2019 21:16:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728128AbfAXVP5 (ORCPT ); Thu, 24 Jan 2019 16:15:57 -0500 Received: from mail-pf1-f195.google.com ([209.85.210.195]:38160 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728071AbfAXVP4 (ORCPT ); Thu, 24 Jan 2019 16:15:56 -0500 Received: by mail-pf1-f195.google.com with SMTP id q1so3630507pfi.5 for ; Thu, 24 Jan 2019 13:15:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=jfPDsizXFvuEx4Zf2R7rWTHRSgVVFK955p3ms6TglQo=; b=D82j1sHKK3TRkYNHfcY/bZZuek1N9eLTp/LtInXcIH74XxdkU/9dIRvu5dF5YR46X1 G7dGafKoXB9lDZ95hhNpeoJYOC/PMAvCr/u6od/jKyFzSTgVQ9KREUCpJgyKn6mkdOdN C1HpOpFEK3H9wTfZ3MY6u7Q7aJ7UDnSIemLa9F/+Sazr/jvqdmMOBBb17OG0DykBPqkQ hsKrHb8LHYP4Lfa1jhBgWY44v8tzWhfu87nYJWzisxkAc/Ugflu0KeszaX6I1NRPH7LD 10h5p3RjA7sXAlFAbbAmOCviMd0C/Acd0Z0Jsue2OhngekXL/RKhYP3AU1F3nLYlWGo2 kqig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=jfPDsizXFvuEx4Zf2R7rWTHRSgVVFK955p3ms6TglQo=; b=sAknblIb/YkKJDzEUNFlvLxjwqRvmOiBl6i2GQwt+JSjuwy1oMk8fbQyNvi24XSPRX CT2ey4uuP7dhfVxJFBP6tM4rm/22SM1hcXRyi+ux5mRLN2kZ61kBR3oAWjmPCwaJK8x1 zZYPyBq3EzUuj7qf4d0kH7WtBz/6tZGS+NhzG6gntspEzVgKEca0DyFlGqovji9qPJ5z Jx0Dvi8wk6XdzHvYQlXW7ncbpvgVFiDpoC5g1NCqAoMXvl1TzBsYHtOOHHgmf4d+DKWY Sy5KFXuOkIXwkyKOjDW/zpf/p9o6QzdhxYbyxcfOIUg6fUKLbApiWHF9CAt9/YssO2jX Aj2g== X-Gm-Message-State: AJcUukccyUe8/sPM8n9a0PnALDl7lqaUWYi7vMauzbKUZ1bNKMA5+Q12 zwMy7s5jOTdTpBmfNjmRxRDXTA== X-Google-Smtp-Source: ALg8bN68x9T0eJokG1BPGt0R+4pOEjGNnsNqCOTW3GuWSp2tGAwkcmDKIni0+LaYE36dkvV+NfNAng== X-Received: by 2002:a62:1f53:: with SMTP id f80mr8135910pff.92.1548364553045; Thu, 24 Jan 2019 13:15:53 -0800 (PST) Received: from surenb0.mtv.corp.google.com ([2620:0:1000:1612:3320:4357:47df:276b]) by smtp.googlemail.com with ESMTPSA id j197sm29626418pgc.76.2019.01.24.13.15.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Jan 2019 13:15:52 -0800 (PST) From: Suren Baghdasaryan To: gregkh@linuxfoundation.org Cc: tj@kernel.org, lizefan@huawei.com, hannes@cmpxchg.org, axboe@kernel.dk, dennis@kernel.org, dennisszhou@gmail.com, mingo@redhat.com, peterz@infradead.org, akpm@linux-foundation.org, corbet@lwn.net, cgroups@vger.kernel.org, linux-mm@kvack.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@android.com, Suren Baghdasaryan Subject: [PATCH v3 5/5] psi: introduce psi monitor Date: Thu, 24 Jan 2019 13:15:18 -0800 Message-Id: <20190124211518.244221-6-surenb@google.com> X-Mailer: git-send-email 2.20.1.321.g9e740568ce-goog In-Reply-To: <20190124211518.244221-1-surenb@google.com> References: <20190124211518.244221-1-surenb@google.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org Psi monitor aims to provide a low-latency short-term pressure detection mechanism configurable by users. It allows users to monitor psi metrics growth and trigger events whenever a metric raises above user-defined threshold within user-defined time window. Time window and threshold are both expressed in usecs. Multiple psi resources with different thresholds and window sizes can be monitored concurrently. Psi monitors activate when system enters stall state for the monitored psi metric and deactivate upon exit from the stall state. While system is in the stall state psi signal growth is monitored at a rate of 10 times per tracking window. Min window size is 500ms, therefore the min monitoring interval is 50ms. Max window size is 10s with monitoring interval of 1s. When activated psi monitor stays active for at least the duration of one tracking window to avoid repeated activations/deactivations when psi signal is bouncing. Notifications to the users are rate-limited to one per tracking window. Signed-off-by: Suren Baghdasaryan Signed-off-by: Johannes Weiner --- Documentation/accounting/psi.txt | 104 ++++++ include/linux/psi.h | 10 + include/linux/psi_types.h | 59 ++++ kernel/cgroup/cgroup.c | 107 +++++- kernel/sched/psi.c | 562 +++++++++++++++++++++++++++++-- 5 files changed, 808 insertions(+), 34 deletions(-) diff --git a/Documentation/accounting/psi.txt b/Documentation/accounting/psi.txt index b8ca28b60215..6b21c72aa87c 100644 --- a/Documentation/accounting/psi.txt +++ b/Documentation/accounting/psi.txt @@ -63,6 +63,107 @@ tracked and exported as well, to allow detection of latency spikes which wouldn't necessarily make a dent in the time averages, or to average trends over custom time frames. +Monitoring for pressure thresholds +================================== + +Users can register triggers and use poll() to be woken up when resource +pressure exceeds certain thresholds. + +A trigger describes the maximum cumulative stall time over a specific +time window, e.g. 100ms of total stall time within any 500ms window to +generate a wakeup event. + +To register a trigger user has to open psi interface file under +/proc/pressure/ representing the resource to be monitored and write the +desired threshold and time window. The open file descriptor should be +used to wait for trigger events using select(), poll() or epoll(). +The following format is used: + +