Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp835028ybl; Wed, 29 Jan 2020 10:27:19 -0800 (PST) X-Google-Smtp-Source: APXvYqznDH4CU2OhLktd3EZHbvv3dP7wKbwn5gwS7dM889xDmgB6cFEDaDfSLGX5fOAjIhGLSqIa X-Received: by 2002:aca:4994:: with SMTP id w142mr169566oia.178.1580322439160; Wed, 29 Jan 2020 10:27:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580322439; cv=none; d=google.com; s=arc-20160816; b=kbkA/d08sBTo2270ltdvJDymKj/unS1W0kDeqU6xG4mKb3agqB4cEBISJ9cCu+mHIV SWK5lotojdJy8CcmOye0KduNl8bnPx2WNq8v9LU22x/3HC8riO3OM+rWWoCy3OueYHJj ttFWi22adNkY8YjWikjKnQkcf62hgGE/ZgW/1ErLT3CMuifD3vyVymhkT2a6RVSqNV0b ymt4zbThgzySg4eMA/ML7PxAreygDAXe4VZ4Yq21YNzBGoa1znhJ6bxrJOTW50pwgvHv +IkEl2RLiki/veYkPjOOjjyMcspRrfV0OQKPcr9Zh1C1ybzKbx6ldhFzZUBsyi/nmoV7 eyUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=pP3KA7M8snq5o9/vtxUh5GwuQDC/+wXU1/Q1jYP2R48=; b=BQKG0C2V+yVJ95nUKhF5A/KA4H5CsZek/bob5O5I2uraMvvR2GYwGC2/CpSHwPf6gX VKLDFa7b3VV+n53GD4GuoT+OM/963i0ZLxIRg+HvMVXBxXwHLZSJelvKgzS/Mj8UPC/c dDSJDumdMVw13JtaJN8seE1+FJkXdKwMCb7QsgF+/nH3HT6VXwsdEFuobQI8VwSonG7r mVa9oEdUwMcv1jxM9KP0hVMB8M93zVqc7xnunoauBHHxcdNHpwY+XAsJJszujSqWMmd4 i4juXMqv46HuqqxDl+g4Iz4bvU67mY6N8wC0ZrF/G2sWOTTfrU0r99wJxkiaCZCNqKLt igkw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a12si1343343oie.87.2020.01.29.10.27.06; Wed, 29 Jan 2020 10:27:19 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727477AbgA2SYr (ORCPT + 99 others); Wed, 29 Jan 2020 13:24:47 -0500 Received: from mx2.suse.de ([195.135.220.15]:45752 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727107AbgA2SYr (ORCPT ); Wed, 29 Jan 2020 13:24:47 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 5F52DAECB; Wed, 29 Jan 2020 18:24:45 +0000 (UTC) From: Davidlohr Bueso To: song@kernel.org Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, dave@stgolabs.net, Davidlohr Bueso Subject: [PATCH] md: optimize barrier usage for Rmw atomic bitops Date: Wed, 29 Jan 2020 10:14:37 -0800 Message-Id: <20200129181437.25155-1-dave@stgolabs.net> X-Mailer: git-send-email 2.16.4 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org For both set and clear_bit, we can avoid the unnecessary barrier on non LL/SC architectures, such as x86. Instead, use the smp_mb__{before,after}_atomic() calls. Signed-off-by: Davidlohr Bueso --- drivers/md/md.c | 2 +- drivers/md/raid10.c | 7 ++++--- drivers/md/raid5.c | 9 +++++---- 3 files changed, 10 insertions(+), 8 deletions(-) diff --git a/drivers/md/md.c b/drivers/md/md.c index 4824d50526fa..4ed2eb6933f7 100644 --- a/drivers/md/md.c +++ b/drivers/md/md.c @@ -2561,7 +2561,7 @@ static bool set_in_sync(struct mddev *mddev) * Ensure ->in_sync is visible before we clear * ->sync_checkers. */ - smp_mb(); + smp_mb__before_atomic(); set_bit(MD_SB_CHANGE_CLEAN, &mddev->sb_flags); sysfs_notify_dirent_safe(mddev->sysfs_state); } diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c index ec136e44aef7..1993a1958c75 100644 --- a/drivers/md/raid10.c +++ b/drivers/md/raid10.c @@ -1865,9 +1865,10 @@ static int raid10_remove_disk(struct mddev *mddev, struct md_rdev *rdev) /* We must have just cleared 'rdev' */ p->rdev = p->replacement; clear_bit(Replacement, &p->replacement->flags); - smp_mb(); /* Make sure other CPUs may see both as identical - * but will never see neither -- if they are careful. - */ + /* Make sure other CPUs may see both as identical + * but will never see neither -- if they are careful. + */ + smp_mb__after_atomic(); p->replacement = NULL; } diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index ba00e9877f02..3ad6209287cf 100644 --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -364,7 +364,7 @@ static int release_stripe_list(struct r5conf *conf, int hash; /* sh could be readded after STRIPE_ON_RELEASE_LIST is cleard */ - smp_mb(); + smp_mb__before_atomic(); clear_bit(STRIPE_ON_RELEASE_LIST, &sh->state); /* * Don't worry the bit is set here, because if the bit is set @@ -7654,9 +7654,10 @@ static int raid5_remove_disk(struct mddev *mddev, struct md_rdev *rdev) /* We must have just cleared 'rdev' */ p->rdev = p->replacement; clear_bit(Replacement, &p->replacement->flags); - smp_mb(); /* Make sure other CPUs may see both as identical - * but will never see neither - if they are careful - */ + /* Make sure other CPUs may see both as identical + * but will never see neither - if they are careful + */ + smp_mb__after_atomic(); p->replacement = NULL; if (!err) -- 2.16.4