Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp524663pxj; Thu, 10 Jun 2021 06:37:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzv3kBEuYN212BfsjNXc7dKeooRhbIzxzhfH8tJn1HIw/7neBeCiGHmU8HE0aJxV7tJGMXX X-Received: by 2002:a05:6402:1b04:: with SMTP id by4mr4983142edb.238.1623332258419; Thu, 10 Jun 2021 06:37:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623332258; cv=none; d=google.com; s=arc-20160816; b=cqOcUiM458ezfKPHtFINJTywyg19w29MvwJNltnK9FKaGlai6HXI63vTM990z7DYm5 w8xn6WDh+597h2fZNP0OT3zPT3rZ/jiuF1jIyasC/y4yQCHuVxVoPMeiC4KY6Sg2kRn/ WY3S65nwM6t3imQfhVji8GPoARVmZY/RFHzGvkWLMSuZ62s+wI6dCWXnrwOLyyLS7kJx //TWmrpQrbabWSwbR0kFyXbILrz5+MQONUyoNTnsHp8ce36gIAbBqA85GzuMohnPcMex nsHPLwcQERvIivIjePxZphGqk5wMHq4KDgWMiv6U/r01GIIycQ+JpTyKNuPCZ+7eLcx8 WvTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=odZpK3wBmNb+oChc/OsEJRGBvHX2Z4TZ6UKHYY5n+s4=; b=tCAjHAYX3eqAkPUL7zgo80O+7bGUrZ0dVJnYAteaGZcseGoPkJmwgZKK+zElx00hCl 05pX5gMe+N5Mq9EopCbKuYGVuheC5unKad04GhJAUMs6FA6mZVMqiQXx0MQYYSqQg424 P5rFKW2VDuq9k/fF8Q81VCSd9XByeQFqHhYzc0WHcLOp/SizlvV4yo56fBoJU9dVPann h46LYVNUvF2mF+JUrMhQEERONAstSFuEeehBR2/QdQDquCDD0c+nFnhfVu7sRRiroXSW gxYIGkyHD2EV7c+2EojNQ0MrS/tVB23ya5kj3Ed8t1A3HK+kqx1PJptjzL3YIDo2KS4h ZUYA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id yw6si2233538ejb.464.2021.06.10.06.37.14; Thu, 10 Jun 2021 06:37:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230329AbhFJNgA (ORCPT + 99 others); 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.