From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A3F0AEB64D7 for ; Wed, 21 Jun 2023 21:23:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230235AbjFUVXY (ORCPT ); Wed, 21 Jun 2023 17:23:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44454 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229632AbjFUVXV (ORCPT ); Wed, 21 Jun 2023 17:23:21 -0400 Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 799DE171C; Wed, 21 Jun 2023 14:23:20 -0700 (PDT) Received: by mail-io1-xd29.google.com with SMTP id ca18e2360f4ac-780c8df59caso15776339f.3; Wed, 21 Jun 2023 14:23:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687382600; x=1689974600; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=I4rxMNbWqvL7SlrQRGe8uFSm6XpuYw7vzKHdGgmcjiI=; b=MSf3PCXq6wdLohcP9gMgCzMabwUNVmiy4Osu4b3QDHklikztVAPUZkOPJaihAdm1z4 cKDA/Zb36eDxDxF/+j92qnBpKTjKp9o8FPaqZaPw4KdEaiTPHoy8t0rCXJ/ytda3tKtS wUi42M5xqm0IeiQ6aF096aYo7xjYAzNDPdOS1HVoaOmwnvVVQ3GdmoT9oVj60i3UeOnK nBnJFEZHfvRvi++CwEzljmyCohdD2tZQ5aSD4piwJDOvGgrayNoUkG0oGTpYoN3coPJM aAyoM8KEMMRJgcckSr6tUgfo4L5r2FuiKEssu4ZqtvoZc2Ye5PuZw+l4sSxXQhS/NpRR cf/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687382600; x=1689974600; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=I4rxMNbWqvL7SlrQRGe8uFSm6XpuYw7vzKHdGgmcjiI=; b=f1Ge2RcBheRk7v3qw5gCfwjAV4H8VvVZ2c+R15Vopt+z4PzdcyZs+qSMezshuQdk7t vl1acXPKKvHmFs/r6MMLwNA4+DZ2ZM10xD1OeCQejHYHRwSap9g9NnzFPFV5kKt3Z3dl P8M7R7jH2j/g19I3XTBYq/bv9Jw3uKtzAqGsapT8Pm0UE5K8ttDQEmN+EdQWSc9T6IDR cWToHaKcCrW76xyvEL2wzCBmCoR5+A+A1BtRDxn3s6nZbdt7sIdYy3epYDiIZAQeUX8M HkGKyoi/r9U7XH2gr67iBUNCkvHWIgl2aOG1kEZ72yE8dt4D66RGwbdfai6u+UNImg8X wYMQ== X-Gm-Message-State: AC+VfDweNU1Bu6BpCcOLv27FUfLvoownUoymE59+Y8SRE2kWkdlbsrjo l/0m6Bq1+Ey3sPmB0ijbg78= X-Google-Smtp-Source: ACHHUZ59vHYbRmPv7y5qCCQCB5u/mULMuwGcmFXF++o1FnUnV7zSBzGuHPvW43JW6pHWJIZSlGXThg== X-Received: by 2002:a92:c10a:0:b0:340:774d:cf79 with SMTP id p10-20020a92c10a000000b00340774dcf79mr16219310ile.6.1687382599636; Wed, 21 Jun 2023 14:23:19 -0700 (PDT) Received: from localhost (dhcp-72-235-13-41.hawaiiantel.net. [72.235.13.41]) by smtp.gmail.com with ESMTPSA id t13-20020a056e02010d00b00341e955a541sm1581631ilm.16.2023.06.21.14.23.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Jun 2023 14:23:19 -0700 (PDT) Sender: Tejun Heo Date: Wed, 21 Jun 2023 11:23:17 -1000 From: Tejun Heo To: Josh Don Cc: Peter Zijlstra , Zefan Li , Johannes Weiner , Ingo Molnar , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Daniel Bristot de Oliveira , Valentin Schneider , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, mkoutny@suse.com Subject: Re: [PATCH v3 2/2] sched: add throttled time stat for throttled children Message-ID: References: <20230620183247.737942-1-joshdon@google.com> <20230620183247.737942-2-joshdon@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230620183247.737942-2-joshdon@google.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 20, 2023 at 11:32:47AM -0700, Josh Don wrote: > We currently export the total throttled time for cgroups that are given > a bandwidth limit. This patch extends this accounting to also account > the total time that each children cgroup has been throttled. > > This is useful to understand the degree to which children have been > affected by the throttling control. Children which are not runnable > during the entire throttled period, for example, will not show any > self-throttling time during this period. > > Expose this in a new interface, 'cpu.stat.local', which is similar to > how non-hierarchical events are accounted in 'memory.events.local'. > > Signed-off-by: Josh Don Acked-by: Tejun Heo Thanks. -- tejun