From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Remove unnecessary memory barrier
Date: Wed, 04 Sep 2013 16:27:57 +0100 [thread overview]
Message-ID: <1378308477.2740.32.camel@menhir> (raw)
In-Reply-To: <1554021184.19774670.1374760429690.JavaMail.root@redhat.com>
Hi,
On Thu, 2013-07-25 at 09:53 -0400, Bob Peterson wrote:
> Hi,
>
> Function test_and_clear_bit implies a memory barrier, so subsequent
> memory barriers are unnecessary.
>
> Regards,
>
> Bob Peterson
> Red Hat File Systems
>
Now in the -nmw tree. Thanks,
Steve.
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> ---
> diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
> index 9435384..a45b1e0 100644
> --- a/fs/gfs2/glock.c
> +++ b/fs/gfs2/glock.c
> @@ -1411,7 +1411,6 @@ __acquires(&lru_lock)
> if (demote_ok(gl))
> handle_callback(gl, LM_ST_UNLOCKED, 0, false);
> WARN_ON(!test_and_clear_bit(GLF_LOCK, &gl->gl_flags));
> - smp_mb__after_clear_bit();
> if (queue_delayed_work(glock_workqueue, &gl->gl_work, 0) == 0)
> gfs2_glock_put_nolock(gl);
> spin_unlock(&gl->gl_spin);
>
prev parent reply other threads:[~2013-09-04 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54448320.19773408.1374760351761.JavaMail.root@redhat.com>
2013-07-25 13:53 ` [Cluster-devel] [GFS2 PATCH] GFS2: Remove unnecessary memory barrier Bob Peterson
2013-09-04 15:27 ` Steven Whitehouse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1378308477.2740.32.camel@menhir \
--to=swhiteho@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).