Received: by 2002:a05:6358:111d:b0:dc:6189:e246 with SMTP id f29csp1829240rwi; Thu, 3 Nov 2022 09:29:52 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7V63hrNznkCp55zK5IwpTJJqa66OsV4SuOsEEEojLLcr0dGJZobeMvkYW6KYi9yNzS/wUe X-Received: by 2002:a17:907:2d29:b0:7ad:b388:df3c with SMTP id gs41-20020a1709072d2900b007adb388df3cmr28280877ejc.45.1667492992549; Thu, 03 Nov 2022 09:29:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1667492992; cv=none; d=google.com; s=arc-20160816; b=pWOy38TPrxfdk6f6K2Srm3jZRhllgmVQOurRB70GJR6nBjutI70BwM+7bELo28uXSS 81fpn3MayOhDNvs7VDqPGrXyT1U64uazz8DImm+nKGljuCG1R4tLDBLDymD2XRFW346g kJl/Bf3tmBOXfBgwll2p53B3s7r2PlYUC7cvCSFn0UDoBcSBm3d2oUL3rt2VIw3cq2kT eI3syezXA3/eI0kDSVZOZX23ixn+UjCbIMMPOnyOelyResj0uZZmm2YXc5oH0e5eJvm1 D4AfHJrvd/z88WW12YlKjXQIGAzxiv2ijp5o5nsiF9As/AvlTxgAhNchWTRbVWlET41V ocKw== 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=tt/lBSJ07NTr/8w7hhp+nZAob7j7Xiq0qJ8m0UH5/hU=; b=sp5ULccjmVNx1pR7/uzyZoOKTaFFbtQK2Bsdh3DQw5a/XRkWUssIaGNmEE6U5uVJFO 9zS1Q88TZCovFt8lajssC/so3hJNCgKINyP+ulU4CdKkwVOUN1+SfYnJ2T0TlfkpqpI4 r+mPWnk0DknSzy6arSf3lZpKXZc9wKleiGSPXxozXBAveLlPtfKypsAPXrq2ig+itLHV d6IPwRX0x+Wn14NjDs8x28EZ/qvpF7k24jAzrS8OQTWXkWJZUYhBV26qOHoh9prtJg03 DrIxCZuPou07F5OP7/q75S2qghroGggCuWVWy/ptoY7tIdxpXEhplTrQyah+GMQJM2UG cVvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=quHYiChP; 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 mp27-20020a1709071b1b00b007a8dddc7ec8si2060788ejc.382.2022.11.03.09.29.28; Thu, 03 Nov 2022 09:29:52 -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=quHYiChP; 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 S231580AbiKCQ0n (ORCPT + 97 others); Thu, 3 Nov 2022 12:26:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50696 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230291AbiKCQ0i (ORCPT ); Thu, 3 Nov 2022 12:26:38 -0400 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AA8A1DF0C for ; Thu, 3 Nov 2022 09:26:37 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id 21so3875991edv.3 for ; Thu, 03 Nov 2022 09:26:37 -0700 (PDT) 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=tt/lBSJ07NTr/8w7hhp+nZAob7j7Xiq0qJ8m0UH5/hU=; b=quHYiChPb0Skd4UIuRGNpR9MbACvRzfrTff2KYgZMeH1TnKNWkV3gnKLRt4qxuItKf YaAo1VtOP8uCKfoGX3pV8CaLkX2MwXikncLam1oX6JEfT9tqq+lK+jyQT0rIPskfHFz3 OVnMZf+5zhO5OSiDpoPXwJ7mu/VdUdM64GQ5x0kk3w9hPo+zNXvBwq7SccYSSnyx4dKM XmTqzf9KXpIreBCKPTvZebeVpKydna10/mBnerbmFczViYUtcKEB0Q2AAofDyUOfDsea wPk1fWl6DJSAv773+Wg5np6epQe9JIwFcPw7VYYg03srOEEouAdVNnppcaa+utCqeMp7 81TQ== 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=tt/lBSJ07NTr/8w7hhp+nZAob7j7Xiq0qJ8m0UH5/hU=; b=Em6jW/lDN8pyyS+FKGOgR2pYiZJcMiZ7x+qKaBAAIVo+11bvmp8/RukUwXQy1N1wMQ EqRppGD3gM+t+IwUKXHvAx6xbFWwhRJeprdUFtMv/uHgg+78mmp+SRWKn/WcYpMYND6W Tqy1yvUs9qmv/gRHXKtgQpQV9ECRdx6cKDvUClR5ZL3FhE0qTAvbg5yczngvvR4Do8lc ZWCd4sPWHvSYuIg/pbTQGyNCc076h/nsJtJIfDGZrY4nSvE9/0CzRRl3KKBgBAPChapS KGrl+5cC07XCQjWRdJkitZlg+IAPCTz6M4tWCZJdbgl5kqK3RmNh9AxGhpS8X/rMiM12 ICQg== X-Gm-Message-State: ACrzQf3IWJnbHzNuxUXCx2wg7RU8KDykdyJti7Y9NfMw0RtRliQuEXO6 lQXlzpMQNQgROK10GoAJXjyDkg== X-Received: by 2002:a05:6402:51a:b0:461:970e:2adc with SMTP id m26-20020a056402051a00b00461970e2adcmr30802753edv.44.1667492796209; Thu, 03 Nov 2022 09:26:36 -0700 (PDT) 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 kx9-20020a170907774900b0078116c361d9sm702507ejc.10.2022.11.03.09.26.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Nov 2022 09:26:35 -0700 (PDT) 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, Paolo Valente Subject: [PATCH V6 0/8] block, bfq: extend bfq to support multi-actuator drives Date: Thu, 3 Nov 2022 17:26:15 +0100 Message-Id: <20221103162623.10286-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, this V6 differs from V5 in that it addresses the issue reported 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/202210301803.9wm3k7D8-lkp@intel.com/T/#m3685011dacaf0801bd084b2a3194c861a4e940ba 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 | 97 +++++---- block/bfq-iosched.c | 521 ++++++++++++++++++++++++++++++-------------- block/bfq-iosched.h | 141 +++++++++--- block/bfq-wf2q.c | 2 +- 4 files changed, 528 insertions(+), 233 deletions(-) -- 2.20.1