Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp5978568iog; Thu, 23 Jun 2022 08:56:27 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tMPJvH7UNKPuF46TnDhDXiUM+/++DOE1TDHZmKgqzjn9btvfZJLyFb+FccI6GYxyq+b6Aa X-Received: by 2002:a17:906:7a4e:b0:722:e68b:3946 with SMTP id i14-20020a1709067a4e00b00722e68b3946mr8894818ejo.515.1655999787010; Thu, 23 Jun 2022 08:56:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655999787; cv=none; d=google.com; s=arc-20160816; b=dGQCDtHl2OTBcygj56l8v/oSNjqhhy62Kw78BSCTAJ+u5oxPYSGPQAXBUfsn+2zuuK ldU7L3HcEUFbqqzSQGPjs2ITGuOKYJYQd6b4hLCMZVn5OwAaAr9toT5T5YNBOWgJB2/+ me3mtHHeXEwDySQx6Sd7JjXe7SqMrSF2HFff5ZVQJuDXymhrsAqJsHiZ6EWlXEeDy5c8 biLqYT0bteckJ/+PSgV52qi+/beC2Im+G3kePBYP2RMHDsKuTc/5P1FOjkkA1B95si37 eSBryVfhFGdRilH8quF79ToxEj5A7c1guVXH2hbzq0BHEWOTLQQJHcmR7sLz8pfFmnk2 37jg== 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=MRHeHRH3cZ/+b6GPkMmzaCrX1eZuqFFPiinOLY5MTlE=; b=UzqzRE5KTU7tgc/fKY4CV0MoHshGYietlkfxpP5RZZVqL0C7qfbbITDY6QOkIqOEkI NvLVgTk6KpaRi0VU7gHvz9jKHgqBqjI6Mim4Ox69FpCC/idc+98Tp7TPm8cd43lpmtxL 8bUgnuRvhHhj4Jm5n45bieMnF8isBFH9YR+iqT3LDRxgStRmU92QfSQU/+p1koFNemxL bb/vNvSM+kSAw5ruz7Ud1tMPqHWpECOPgWlPyUIRXV8Ghtt8FO8qGf6TDkBdzBP3ylR+ tnpjK4FGGREFHfNlIxM+akWH8YfyHGkQaSSOY8flKZEPBsFi7pRmJ69qOS/e+7XFCMEq 0MGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=hdlvhWUm; 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 dr19-20020a170907721300b006fef10b80f3si10770211ejc.112.2022.06.23.08.56.01; Thu, 23 Jun 2022 08:56:26 -0700 (PDT) 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=hdlvhWUm; 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 S231948AbiFWPx7 (ORCPT + 99 others); Thu, 23 Jun 2022 11:53:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58738 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231362AbiFWPx6 (ORCPT ); Thu, 23 Jun 2022 11:53:58 -0400 Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DD7BE2F679 for ; Thu, 23 Jun 2022 08:53:56 -0700 (PDT) Received: by mail-wr1-x42e.google.com with SMTP id w17so28552679wrg.7 for ; Thu, 23 Jun 2022 08:53:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=MRHeHRH3cZ/+b6GPkMmzaCrX1eZuqFFPiinOLY5MTlE=; b=hdlvhWUmoY8QF+THiQiMKSf9mbrg9w85JT7zhHhzY7wNsYx6YrgXZQTRuzF7PQdDqr o3D9i2rd8+4gZ1TENoouV0UNpW4QPimhvWK2iudQ2PH5qIqnCWx9lXSV0EOpjLQXTEbE yfcbURQRZfcTehETyKUADw4a3Zd+3fI3I0c392K2oKyX2fwecptAd4+06z0TcBmk0qTq jNQvxdtUJEVzzf92NfsPUec2AJib5VtSEEm3Vcex+TEBnyZwhTigwT/ZdMWKwa0QEPUa iA3Rz43/ji9q+4IaE71p2XjawKS9qfNUvxxmLmiiOZ3XfIoG6dPDb24Yo1QUNr8ekWlg 9LJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=MRHeHRH3cZ/+b6GPkMmzaCrX1eZuqFFPiinOLY5MTlE=; b=7uNe7Bbc4TeqBWdCF09sSfVPv5fNtA22CyZEcMDkhC6Gj745mjxXWbC12xdr/bJhFC hWq7LSSsQFRUnwSRKdprKKxki5ecg+keibpXrnF4LSo35bL9yo8BndpG3MReMRmXaV4N WNIlKDyDhTmBQp+D2mOIz1dtU05gAHv/g1UiDBo+8faaDPN3yXbdSbCqXU9nCTCcOex3 kXmuxF7VF/00tL0I3hlV6g8UBW1PVBjb2Jr7LOZBi9kXilfoHguPlpVfmnN5LNiltXVU oGgsx35/JvhPbUNhnR6o/em4RfuXxiE0m0EXvwar+2Z3WjGsdWRzekM53u8xzuUK4UCd SchQ== X-Gm-Message-State: AJIora9AaFFwdQZ/622aqlk84iCiKgHC2YK6C9XEPRIHXneYvj6rdbZy CvDv3IgKJ5kL5fyxFA5mybxkhQ== X-Received: by 2002:a5d:4c50:0:b0:21b:a6cf:f699 with SMTP id n16-20020a5d4c50000000b0021ba6cff699mr4866352wrt.668.1655999634599; Thu, 23 Jun 2022 08:53:54 -0700 (PDT) Received: from OPPO-A74.station (net-37-182-48-184.cust.vodafonedsl.it. [37.182.48.184]) by smtp.gmail.com with ESMTPSA id n10-20020adffe0a000000b0021b5861eaf7sm20650830wrr.3.2022.06.23.08.53.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Jun 2022 08:53:53 -0700 (PDT) From: Paolo Valente To: Jens Axboe Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, jack@suse.cz, andrea.righi@canonical.com, glen.valante@linaro.org, arie.vanderhoeven@seagate.com, Paolo Valente Subject: [PATCH 0/8] block, bfq: extend bfq to support multi-actuator drives Date: Thu, 23 Jun 2022 17:53:27 +0200 Message-Id: <20220623155335.6147-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,T_SCC_BODY_TEXT_LINE 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, this patch series extends BFQ so as to optimize I/O dispatch to multi-actuator drives. In particular, this extension addresses the following issue. Multi-actuator 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/ 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: turn scalar fields into arrays in bfq_io_cq block, bfq: turn BFQ_NUM_ACTUATORS into BFQ_MAX_ACTUATORS block/bfq-cgroup.c | 97 +++++---- block/bfq-iosched.c | 488 +++++++++++++++++++++++++++++--------------- block/bfq-iosched.h | 149 ++++++++++---- block/bfq-wf2q.c | 2 +- 4 files changed, 493 insertions(+), 243 deletions(-) -- 2.20.1