Received: by 2002:a05:6358:f14:b0:e5:3b68:ec04 with SMTP id b20csp3828382rwj; Tue, 20 Dec 2022 02:26:11 -0800 (PST) X-Google-Smtp-Source: AA0mqf6Yx5ljr+LBEeJfjgRW/YEuoy/PQMMXGxSkzcGU8yG1hKxSDr2nT7BV2qRZhst+YU+QBQtn X-Received: by 2002:a17:90a:2b82:b0:218:7148:580d with SMTP id u2-20020a17090a2b8200b002187148580dmr47077681pjd.7.1671531971562; Tue, 20 Dec 2022 02:26:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671531971; cv=none; d=google.com; s=arc-20160816; b=xQ+7zkwpexQTVsaO0lQAypZ3Eiuf98hI+3gY8/GR6xl3WpkuhdTotUjiPGgm5PDitr fYk4QWxVO8waRaoZ85F30lX/4vgE1eiL5Ug6is4oQjvklAugp634AXQxFqZ3OcptFxPc Z8p2ws2auyQvfDl2VSEzfxsG4AH6Dd1q6MtvrYtjFO1/L0kSuTifQCd0I35TNXcHpg8F NKS3OLjeeAG0YxRiLM6F5AnQJYgIg8iKlA+bRqG3XXNqoiojUdUaA1X/1MrqKVc4vlZB n5JaFyhDd6KDbyhoAUs7Qi+NPx7TEVrq9dCgl76QwhJT8E+WaqVHjdfGnGgyeFSkeY+h S19Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=7nQuG8pByalhJ70WsUAgrsYOXMyPHv7RuONImTbDvjw=; b=wcTh6HZ/3SadU00cn/sPmZCnLMRg5xKW6SpMeCGCyZHhU0mVQGX3aGo/adq30hrW9+ vP23G0jkgUK03ED63SIJBv0LrupiNeMterueeoquhuGWlJlZLmjI8sVAnOtZpbKYdAWK DWn/eB948FlUcqXMWmnw0XbQb34MOhIco4t+m+A7asY75vt5tRAIAzQXO4GUme8vu48r OZpuTET/ZiRX2fNaBLiC6OYvHWoGVWG/s/F4BgYirL1dtyaV8MjE9DbARVmfwGKeE0LC CYWG5co9GnnohFYYrs+Yrv+K2THl9NlPq/wok1XM9YeZSy0lbGfZvWNZKze8Xca9GR7/ P4XQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Ja97wKts; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m1-20020a17090a34c100b0020382775a6fsi12807354pjf.149.2022.12.20.02.26.01; Tue, 20 Dec 2022 02:26:11 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Ja97wKts; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233289AbiLTJug (ORCPT + 70 others); Tue, 20 Dec 2022 04:50:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233486AbiLTJuZ (ORCPT ); Tue, 20 Dec 2022 04:50:25 -0500 Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 812DE140D8 for ; Tue, 20 Dec 2022 01:50:23 -0800 (PST) Received: by mail-ej1-x635.google.com with SMTP id ud5so27913769ejc.4 for ; Tue, 20 Dec 2022 01:50:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=7nQuG8pByalhJ70WsUAgrsYOXMyPHv7RuONImTbDvjw=; b=Ja97wKtsitFlBh+NaZM2lwnIDGETdb4ZT+7QUe0e5VI1v35CRalZ4U8zO4+y4HqwXU MOime7T/zIEzj0nahK23UJvA1lm2W1UxvUpCVpWNaqTP5on7rxfTUJTG7WtVcFkO/gwB +JbGX8+cTWHk4UyWUKPD/fVGSNk7jI9uyXsgbBh9JctQgV8yQLHh8DTQCs6KHRZOWm5W +O+nqKbP75dHv/x3NT6cQ7BhOgD3GykquwPyB1GChUFj8CfUnl4ts4zgycuynSBtlT6O 8z7RLSjYwuEHHYiduvzXywJ8iT6PVWffRn5qINJPUfAl6H1N7lIwrva/xIdZrd63vjBI vBUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7nQuG8pByalhJ70WsUAgrsYOXMyPHv7RuONImTbDvjw=; b=uDUJqGivHIObCocVpkFBxJAVMHuFJtFc3jXP8lgMnfAP6vbSmBXGFja+uNEgNV5wvN RSGKZCcakQVAtfREpOfIbFTE1nxA2vo69db9FOPjJiUIl/BqbKnb8tWKiVmT7rA6gKSa q1wwbV19/LW2bbJWEYRzNTmvsDct9dU5wf32EueDXeztwJvgmFE2z+zM9V1uZBz+6RVM c14eCltIyZRXxLjf5KgcsaDfRtktqipbQnQ0+r6YYwt/WDudNCMn7dig7ikx+3qmpx/V M3ouZw58j8PYcPSTCucaAeEcfVjJxJGsl1yVPZqx380/MH/rFpPR8tqT9Z0Rgoj5ZVZQ Bqng== X-Gm-Message-State: ANoB5pni0k/XQG9SUVrdJXuiVyR/DL+asSeIGt71iJqeIFhApNpA8Kfk a3VWZUWb43RcMJx9GMfuU9EwSQ== X-Received: by 2002:a17:906:3716:b0:7c0:bbab:22e5 with SMTP id d22-20020a170906371600b007c0bbab22e5mr35828687ejc.16.1671529822049; Tue, 20 Dec 2022 01:50:22 -0800 (PST) Received: from MBP-di-Paolo.station (net-93-70-85-0.cust.vodafonedsl.it. [93.70.85.0]) by smtp.gmail.com with ESMTPSA id c2-20020a17090618a200b0082ea03c395esm1669207ejf.74.2022.12.20.01.50.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Dec 2022 01:50:21 -0800 (PST) From: Paolo Valente To: Jens Axboe Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, arie.vanderhoeven@seagate.com, rory.c.chen@seagate.com, glen.valante@linaro.org, Paolo Valente Subject: [PATCH V11 0/8] block, bfq: extend bfq to support multi-actuator drives Date: Tue, 20 Dec 2022 10:50:05 +0100 Message-Id: <20221220095013.55803-1-paolo.valente@linaro.org> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, here is the V11, it differs from V10 in that it applies the recommendation by Damien in [2]. Here is the whole description of this patch series again. This extension addresses the following issue. Single-LUN multi-actuator SCSI drives, as well as all multi-actuator SATA drives appear as a single device to the I/O subsystem [1]. Yet they address commands to different actuators internally, as a function of Logical Block Addressing (LBAs). A given sector is reachable by only one of the actuators. For example, Seagate’s Serial Advanced Technology Attachment (SATA) version contains two actuators and maps the lower half of the SATA LBA space to the lower actuator and the upper half to the upper actuator. Evidently, to fully utilize actuators, no actuator must be left idle or underutilized while there is pending I/O for it. To reach this goal, the block layer must somehow control the load of each actuator individually. This series enriches BFQ with such a per-actuator control, as a first step. Then it also adds a simple mechanism for guaranteeing that actuators with pending I/O are never left idle. See [1] for a more detailed overview of the problem and of the solutions implemented in this patch series. There you will also find some preliminary performance results. Thanks, Paolo [1] https://www.linaro.org/blog/budget-fair-queueing-bfq-linux-io-scheduler-optimizations-for-multi-actuator-sata-hard-drives/ [2] https://lore.kernel.org/lkml/7125ff61-bf11-6f8c-8496-f2603371c214@kernel.dk/T/#mf28d4c2d5c5265b9bbf3bacbf0ebb2f9e4b907f5 Davide Zini (3): block, bfq: split also async bfq_queues on a per-actuator basis block, bfq: inject I/O to underutilized actuators block, bfq: balance I/O injection among underutilized actuators Federico Gavioli (1): block, bfq: retrieve independent access ranges from request queue Paolo Valente (4): block, bfq: split sync bfq_queues on a per-actuator basis block, bfq: forbid stable merging of queues associated with different actuators block, bfq: move io_cq-persistent bfqq data into a dedicated struct block, bfq: turn bfqq_data into an array in bfq_io_cq block/bfq-cgroup.c | 93 +++---- block/bfq-iosched.c | 577 ++++++++++++++++++++++++++++++-------------- block/bfq-iosched.h | 142 ++++++++--- block/bfq-wf2q.c | 2 +- 4 files changed, 560 insertions(+), 254 deletions(-) -- 2.20.1