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 X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CD7B6C47094 for ; Thu, 10 Jun 2021 13:34:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AAFCF60FF0 for ; Thu, 10 Jun 2021 13:34:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230393AbhFJNgA (ORCPT ); Thu, 10 Jun 2021 09:36:00 -0400 Received: from foss.arm.com ([217.140.110.172]:60166 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230188AbhFJNf7 (ORCPT ); Thu, 10 Jun 2021 09:35:59 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 22FCF106F; Thu, 10 Jun 2021 06:34:03 -0700 (PDT) Received: from e120325.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id D8D213F73D; Thu, 10 Jun 2021 06:34:01 -0700 (PDT) Date: Thu, 10 Jun 2021 14:33:59 +0100 From: Beata Michalska To: Peter Zijlstra Cc: Joel Fernandes , Valentin Schneider , Quentin Perret , LKML , Qais Yousef , Vincent Guittot , Viresh Kumar Subject: Re: iowait boost is broken Message-ID: <20210610133358.GB30309@e120325.cambridge.arm.com> References: <20210607191031.GA12489@e120325.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 08, 2021 at 07:46:54PM +0200, Peter Zijlstra wrote: > On Mon, Jun 07, 2021 at 08:10:32PM +0100, Beata Michalska wrote: > > So back to the expectations. > > The main problem, as I see it, is what do we actually want to achieve with > > the I/O boosting? Is it supposed to compensate the time lost while waiting > > for the I/O request to be completed or is is supposed to optimize the rate > > at which I/O requests are being made. > > The latter, you want to increase the race of submission. > > > Do we want to boost I/O bound tasks by > > default, no limits applied or should we care about balancing performance > > vs power ? And unless those expectations are clearly stated, we might not > > get too far with any changes, really. > > You want to not increase power beyond what is needed to match the rate > of processing I suppose. This is what I took as a baseline for my playground. This tough means we will be are operating on some assumptions (unless we go for some major rework) and that boosting may not reach the highest level in some cases. For those, I guess we will have to use another way to deal with performance. Thanks for your comments. --- BR B.