From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Don't waste time locking lru_lock for non-lru glocks
Date: Wed, 26 Jul 2017 17:11:59 +0100 [thread overview]
Message-ID: <24b4c3d3-7fd6-6294-fd4a-0ccd352274aa@redhat.com> (raw)
In-Reply-To: <563121229.34658408.1501085419976.JavaMail.zimbra@redhat.com>
Hi,
Looks good.
Acked-by: Steven Whitehouse <swhiteho@redhat.com>
Steve.
On 26/07/17 17:10, Bob Peterson wrote:
> Hi,
>
> Before this patch, glock_dq would call gfs2_glock_remove_from_lru.
> For glocks that are never put on the LRU, such as the transaction
> glock, this just takes the spin_lock, determines there's nothing to
> be done because the list is empty, then unlocks again. This was
> causing unnecessary lock contention on the lru_lock spin_lock.
> This patch adds a check for GLOF_LRU in the glops before taking
> the spin_lock, thus reducing lru_lock contention.
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> ---
> diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
> index c38ab6c81898..1029340fc8ba 100644
> --- a/fs/gfs2/glock.c
> +++ b/fs/gfs2/glock.c
> @@ -150,6 +150,9 @@ void gfs2_glock_add_to_lru(struct gfs2_glock *gl)
>
> static void gfs2_glock_remove_from_lru(struct gfs2_glock *gl)
> {
> + if (!(gl->gl_ops->go_flags & GLOF_LRU))
> + return;
> +
> spin_lock(&lru_lock);
> if (!list_empty(&gl->gl_lru)) {
> list_del_init(&gl->gl_lru);
>
prev parent reply other threads:[~2017-07-26 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <842931352.34658265.1501085354071.JavaMail.zimbra@redhat.com>
2017-07-26 16:10 ` [Cluster-devel] [GFS2 PATCH] GFS2: Don't waste time locking lru_lock for non-lru glocks Bob Peterson
2017-07-26 16:11 ` 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=24b4c3d3-7fd6-6294-fd4a-0ccd352274aa@redhat.com \
--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).