Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2435195rwb; Fri, 9 Dec 2022 01:59:07 -0800 (PST) X-Google-Smtp-Source: AA0mqf6amkUfNx7PnnAP1nCAnT+3CDs1uICoBkcKem30t/Y5S5lY7/J0rEOl2kTlEZChon5O3xGd X-Received: by 2002:a17:907:2179:b0:7c0:f90f:163d with SMTP id rl25-20020a170907217900b007c0f90f163dmr4288439ejb.11.1670579946775; Fri, 09 Dec 2022 01:59:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670579946; cv=none; d=google.com; s=arc-20160816; b=O0YTY/3iLuWS4sroEFEMqzSG8iCmWXltM4hnHdn7Hst29Avodx218XAvDOztFxs3/Y BeD7eZKoYAFeKssyV/GFWpxrCjGJ4hr5QdUq6IGblkurrgOdcCH9albuBTg16AOedY/x djKwS3rE5Wy+OxUENKm95/iqEqOT6X5FDr7siXuT+uTsgovR8pBrvFUrKwo1n8SamSbN egVZi9hJu/RlwLbuq/G6UdRtwUna7uVR+5eq5eeuALtyQX7/5iBq43OCR+gXUPvap0ch DZjDbhaSRqrPU9O0a+z6DsVgHZ3Fna7GsG9/dTtsezs/FIdho6SuwvJY3VjPsVwv7ynW twLg== 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=pfI4vsEkYZcvS0kTttCan8tA6wqo2c0ZacXpsvLTWzM=; b=suVfiGAURFyNh34GTkNM4QoU2+6aXH+uLIfMPgtrDMiwuDaZs+Il5wkosaX8Nj/dIE 0M9hEusC5j+Z382NOYN8/2Wxn8BOM19XM4WVvvodLDT88bQJAt57QIaxUolTXQHB1YyN +/sfPDF6LtsIShJRYjAasg1NEqZywoK5Xq7/w6QjxvzO8neLF798lRSVAlTcO9nWJMF2 ZfAoXYNcsdEtl8elZL2stBvyThTzM8xokCcfpj+cQRgc9sy06dLCcgdcYKfeP4EZrjO/ ZiXZu1PVwBFa/P0/ULS7qlGFVjuvkesHar/wEf/F31OM/quN7Oo1Ap7muV+7fFhDrq4l ia0g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=XcarWuHZ; 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 b12-20020a0564021f0c00b0046b1c26d81dsi1051671edb.80.2022.12.09.01.58.48; Fri, 09 Dec 2022 01:59:06 -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=XcarWuHZ; 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 S229760AbiLIJox (ORCPT + 73 others); Fri, 9 Dec 2022 04:44:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54332 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229563AbiLIJou (ORCPT ); Fri, 9 Dec 2022 04:44:50 -0500 Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 959835F6DE for ; Fri, 9 Dec 2022 01:44:49 -0800 (PST) Received: by mail-ed1-x535.google.com with SMTP id d20so2435147edn.0 for ; Fri, 09 Dec 2022 01:44:49 -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=pfI4vsEkYZcvS0kTttCan8tA6wqo2c0ZacXpsvLTWzM=; b=XcarWuHZMTRs5AOZBw/0jYp1FkwxKFBjVogjXX1mlauUBECcasU88p8X5sQGIwxqnB NJ2tT7sWa7WhDscBCcic1qSZsWBonbjM22q93xqiQuRaBA+bLGzZSSVmjouaTE0f6Bjm mu+TLpuhfiy5LTc1VK3X281sLZKHBL/inEkfdu4WXAxeqHnprdhpNCll+dV8d8JE1vT2 IpFtcMrSprl1wbrYqB8akJ4nOvdJLuHiOu6W2VTlJABn+Kw+mlp54+Uu2mKM9lcugVd+ kBcyf78LWC0etYtY+BrVx4d1hYlpaaNtpsiOIBCy3BTvehcQu1kMB9rb2j56wHXaGBdM kT9g== 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=pfI4vsEkYZcvS0kTttCan8tA6wqo2c0ZacXpsvLTWzM=; b=oJacgya8686oY9G7SFUL4fkx0RuEV/o5S4lYARCyB6ko1rK838FoW8knAWXttJYIeC Tg/V9Y2sveqzvaznmKNe5piGhod5cue2J54/ghMZ0WKc53VSjTi5yaV/OnLZYr/0fqeR p4gmhf7KY+hA+qVGplh2p+2Jnb9Fg7SQ5dUYhQHLpRGso1wuvfXyOwfGnknXj0nhKYgb kzD/zF1ZalLhwSNod/+KqoK4B04amTREDL9OmQmeL80GKKIhXGiIFCSQvovLVKufu+qf /j7pQzcjX+OjVkR+GdYUdqIca+AZjnQKHMiTLw1w1ptA5Qjn8AorRDs6eCt6svMFRzOG OC4A== X-Gm-Message-State: ANoB5pnYGZDjEGGnJ5BviX8bIx+s3nKapjde1WBs7VCwBVDDaqfp2Geb f7fAmcut1HysIdIdlR7KR6PZyA== X-Received: by 2002:aa7:c94e:0:b0:467:5491:1e21 with SMTP id h14-20020aa7c94e000000b0046754911e21mr4237385edt.12.1670579088125; Fri, 09 Dec 2022 01:44:48 -0800 (PST) Received: from MBP-di-Paolo.station (net-2-35-55-161.cust.vodafonedsl.it. [2.35.55.161]) by smtp.gmail.com with ESMTPSA id oz18-20020a170906cd1200b007c11f2a3b3dsm353421ejb.107.2022.12.09.01.44.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Dec 2022 01:44:47 -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 V10 0/8] block, bfq: extend bfq to support multi-actuator drives Date: Fri, 9 Dec 2022 10:44:34 +0100 Message-Id: <20221209094442.36896-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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 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 V10, it differs from V9 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/20221208104351.35038-1-paolo.valente@linaro.org/T/#t 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 | 94 +++---- block/bfq-iosched.c | 584 ++++++++++++++++++++++++++++++-------------- block/bfq-iosched.h | 142 ++++++++--- block/bfq-wf2q.c | 2 +- 4 files changed, 566 insertions(+), 256 deletions(-) -- 2.20.1