Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp2211038ybe; Tue, 3 Sep 2019 09:26:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqxsAiNrqmDsvFagl7R2QGY2n1D0unNPO1Vi+YyxKOGQkUHHyIYa5yOHjQn+ypxfNKjks1ij X-Received: by 2002:a17:90a:8c01:: with SMTP id a1mr144260pjo.82.1567528016993; Tue, 03 Sep 2019 09:26:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567528016; cv=none; d=google.com; s=arc-20160816; b=amNUCzV0EdFHWWG5joW6MubGFioXF+7F/GLToqj0fdUEgfFFaWIyvSP2VehqX4VQ/H pzG1oQv35G446hzhCMwRzC8p87z7Mx3utT8QB4W2vIjAPaQWQAO+yts9dVWMoNwWJ9qL gt4Qk8siCnefjvt5Ryzi+Le/yeeuN9/jE4NqHMSL+IvC7d9UMLV+bnhUcuGxY7BiKPq1 uCYMKNI5Y7YA4SkyTNev75IQ7+kmCFtjqPe54AeqKaRnT31RQOhgJ3ZoN+4bom/9duGY A5+chZS1CGjUQuvj07M8mbX5TUyDZfRsCoCKceOYn6sf+posRCBn9ncEWQ1G7s5ItcCY NoMA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=6J8Yzk/bOUO8qaC8KttFTcevzbeROi7XL453ox2DEiI=; b=l59jeJu5G3jRyIt+HBhQmfEfJYUYLGdlfYoG8IYcATZS9k8/LAa6d536CYKfPOm7ze 2hTA9gckIOyMJ6e+kZAH1FeBWKXGcY1ek4sciEtBbBiDIILtTO7R0VtJyLSb3JQe8fhA 5m/n+oBq+XC8N5pyVUIjf8GPDNrVUSZxz/flGQTOr1V1UHqRakK9GDQXMTLYIW0Pbt2h q4qO2vJx6HFR14cUE+nUjsmdpGNgkBTmNczPOm9sjLRQwJ5XRh9Mou7+mZJMjOZr51mv RAMA12JZgR5WmffL7OIU2AP9Cud39X7rF0MqC5sTKEn7LruIxbhF1k5uB2SCfAx1fWaV yNlw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=rP2Ry4O3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j25si17190452pfh.142.2019.09.03.09.26.36; Tue, 03 Sep 2019 09:26:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=rP2Ry4O3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730079AbfICQY1 (ORCPT + 99 others); Tue, 3 Sep 2019 12:24:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:44112 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729692AbfICQY1 (ORCPT ); Tue, 3 Sep 2019 12:24:27 -0400 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A7C6A23431; Tue, 3 Sep 2019 16:24:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567527866; bh=PRw3RDuhrCa64X2CNf+loXfXKXVaqK0V7MFX6ZrbaBY=; h=From:To:Cc:Subject:Date:From; b=rP2Ry4O3QsjL3OUMIhsW2E2NT/d3uio4qLoLPUy3mbcRiGkU0vyFBbu/5cTEsOqM2 V+yI6fc1lCwXrGkgmToYE46BLT6+OmX09vI1U4eCn7QRdJZ6z9NIaVsGARvK22rcqD XXKQXwagNJPEONxgi811zQ96a+i5d4U0WrStXtug= From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Coly Li , Jens Axboe , linux-bcache@vger.kernel.org Subject: [PATCH AUTOSEL 5.2 01/23] bcache: only clear BTREE_NODE_dirty bit when it is set Date: Tue, 3 Sep 2019 12:24:02 -0400 Message-Id: <20190903162424.6877-1-sashal@kernel.org> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Coly Li In bch_btree_cache_free() and btree_node_free(), BTREE_NODE_dirty is always set no matter btree node is dirty or not. The code looks like this, if (btree_node_dirty(b)) btree_complete_write(b, btree_current_write(b)); clear_bit(BTREE_NODE_dirty, &b->flags); Indeed if btree_node_dirty(b) returns false, it means BTREE_NODE_dirty bit is cleared, then it is unnecessary to clear the bit again. This patch only clears BTREE_NODE_dirty when btree_node_dirty(b) is true (the bit is set), to save a few CPU cycles. Signed-off-by: Coly Li Signed-off-by: Jens Axboe --- drivers/md/bcache/btree.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/drivers/md/bcache/btree.c b/drivers/md/bcache/btree.c index 773f5fdad25fb..3fbadf2058a65 100644 --- a/drivers/md/bcache/btree.c +++ b/drivers/md/bcache/btree.c @@ -778,10 +778,10 @@ void bch_btree_cache_free(struct cache_set *c) while (!list_empty(&c->btree_cache)) { b = list_first_entry(&c->btree_cache, struct btree, list); - if (btree_node_dirty(b)) + if (btree_node_dirty(b)) { btree_complete_write(b, btree_current_write(b)); - clear_bit(BTREE_NODE_dirty, &b->flags); - + clear_bit(BTREE_NODE_dirty, &b->flags); + } mca_data_free(b); } @@ -1069,9 +1069,10 @@ static void btree_node_free(struct btree *b) mutex_lock(&b->write_lock); - if (btree_node_dirty(b)) + if (btree_node_dirty(b)) { btree_complete_write(b, btree_current_write(b)); - clear_bit(BTREE_NODE_dirty, &b->flags); + clear_bit(BTREE_NODE_dirty, &b->flags); + } mutex_unlock(&b->write_lock); -- 2.20.1