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 1D07BC71153 for ; Sun, 10 Sep 2023 18:20:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236701AbjIJSUc (ORCPT ); Sun, 10 Sep 2023 14:20:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46732 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230120AbjIJSUb (ORCPT ); Sun, 10 Sep 2023 14:20:31 -0400 Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C159818F for ; Sun, 10 Sep 2023 11:20:26 -0700 (PDT) Received: by mail-wr1-x433.google.com with SMTP id ffacd0b85a97d-31768ce2e81so3705400f8f.1 for ; Sun, 10 Sep 2023 11:20:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=layalina-io.20230601.gappssmtp.com; s=20230601; t=1694370025; x=1694974825; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=MvwmuK6zDdHxLtx5clgb/iLgnTsb5Ioo/98jIe0vnGA=; b=KGHWr6rbu+ye0YoE2kwzD1VRRkkWEcdzuDoMqaOx6R0jjBVYo++MFSLi12QwUjkNJQ 1yPKQoLm14x8C3SyO4rtKdJVBS7XosiGM0Ope2Z0/ivbNZRS5X1tm+BQTvN9bkWoYtU5 +Urryfl4v08n1cxQua3UqKJu0iIWMCI47vMY+ZqX1zGxHlQK7kQjpMWGwFVDmRqfpGoX mIeUWU9UO6sbQoQ5By+31nlAc/Y8IR+OFENuNthoiZvcUswB1+NuKinsi4HC0O18nCgp /Yb8hzRSBglzLJk9Dt8uJsBJqywzlX4XZwsnw08pXhH32iudblp2aRrzW3iDz0xOFbzQ NV+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694370025; x=1694974825; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=MvwmuK6zDdHxLtx5clgb/iLgnTsb5Ioo/98jIe0vnGA=; b=J0r7DI0h4UBEDuqM2yR0hmEDMBDtTzG7bRlq93aqv6RXMwa9MlszGt1r+sU3FPwGeX gbU8FzzDSuVcD0fLEr9PkWV25jJQ33naCcKuhFpABMdSuz+OVaCBMg6UU7LGjrvItLOm /Knro4KZVL5wuCT3Pi2gJg8iencLf5em6yTZMjAzBbo7zSxCYjb9oVhJ5lq+eeCDF9iN WCrd6IxivEf3gzutaryTgcqEMNC10fZSbXzu4jIqCOurufy+mLwCXKwrOhx9syUTuerK q5q6VvGuS/ZnsgFI0doBePWnCqPRZPKCmSKo2yPqd5Qg/Cp16viRfmMPumNXObgOw+Vc 35Gg== X-Gm-Message-State: AOJu0YzgPJ566k5Nh7MRbIB3pqOoO94tqtcwBqAL2nz78k0ltgWUg+xW IIN2hFQw+bkUF2FFed/DEvHwXw== X-Google-Smtp-Source: AGHT+IGzeTX7urFedcuJSmfm2ibmKjyj75DLKVYU44V+a+Vsk9c+iC0EcICiPNkTDKEWD/xg83btSA== X-Received: by 2002:a5d:4b83:0:b0:313:dee2:e052 with SMTP id b3-20020a5d4b83000000b00313dee2e052mr6387818wrt.26.1694370025136; Sun, 10 Sep 2023 11:20:25 -0700 (PDT) Received: from airbuntu (host109-151-228-137.range109-151.btcentralplus.com. [109.151.228.137]) by smtp.gmail.com with ESMTPSA id x14-20020adff0ce000000b00319779ee691sm7767632wro.28.2023.09.10.11.20.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 10 Sep 2023 11:20:24 -0700 (PDT) Date: Sun, 10 Sep 2023 19:20:23 +0100 From: Qais Yousef To: Peter Zijlstra Cc: Lukasz Luba , linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, "Rafael J. Wysocki" , Ingo Molnar , Dietmar Eggemann , Vincent Guittot , Viresh Kumar Subject: Re: [RFC PATCH 0/7] sched: cpufreq: Remove magic margins Message-ID: <20230910182023.hdrhx6b5bq5r4vfo@airbuntu> References: <20230827233203.1315953-1-qyousef@layalina.io> <20230906211850.zyvk6qtt6fvpxaf3@airbuntu> <6011d8bb-9a3b-1435-30b0-d75b39bf5efa@arm.com> <20230907115307.GD10955@noisy.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230907115307.GD10955@noisy.programming.kicks-ass.net> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/07/23 13:53, Peter Zijlstra wrote: > On Thu, Sep 07, 2023 at 08:48:08AM +0100, Lukasz Luba wrote: > > > > Hehe. That's because they're not really periodic ;-) > > > > They are periodic in a sense, they wake up every 16ms, but sometimes > > they have more work. It depends what is currently going in the game > > and/or sometimes the data locality (might not be in cache). > > > > Although, that's for games, other workloads like youtube play or this > > one 'Yahoo browser' (from your example) are more 'predictable' (after > > the start up period). And I really like the potential energy saving > > there :) > > So everything media is fundamentally periodic, you're hard tied to the > framerate / audio-buffer size etc.. > > Also note that the traditional periodic task model from the real-time > community has the notion of WCET, which completely covers this > fluctuation in frame-to-frame work, it only considers the absolute worst > case. > > Now, practically, that stinks, esp. when you care about batteries, but > it does not mean these tasks are not periodic. piecewise periodic? > Many extentions to the periodic task model are possible, including > things like average runtime with bursts etc.. all have their trade-offs. The challenge we have is the endless number of workloads we need to cater for.. Or you think one of these models can actually scale to that? Thanks! -- Qais Yousef