cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Don't add rgrp glocks to the lru
Date: Mon, 15 Jun 2015 12:19:13 +0100	[thread overview]
Message-ID: <557EB4B1.9040000@redhat.com> (raw)
In-Reply-To: <1745858852.16090144.1434133747424.JavaMail.zimbra@redhat.com>

Hi,

On 12/06/15 19:29, Bob Peterson wrote:
> Hi,
>
> The glocks used for resource groups often come and go hundreds of
> thousands of times per second. Adding them to the lru list just
> adds unnecessary contention for the lru_lock spin_lock, especially
> considering we're almost certainly going to re-use the glock and
> take it back off the lru microseconds later. We never want the
> glock shrinker to cull them anyway. This patch bypasses adding
> them to the lru.
>
> Regards,
>
> Bob Peterson
> Red Hat File Systems
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Acked-by: Steven Whitehouse <swhiteho@redhat.com>

Steve.
> ---
> diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
> index 0fa8062..1db06a5 100644
> --- a/fs/gfs2/glock.c
> +++ b/fs/gfs2/glock.c
> @@ -1076,7 +1076,8 @@ void gfs2_glock_dq(struct gfs2_holder *gh)
>   		    !test_bit(GLF_DEMOTE, &gl->gl_flags))
>   			fast_path = 1;
>   	}
> -	if (!test_bit(GLF_LFLUSH, &gl->gl_flags) && demote_ok(gl))
> +	if (!test_bit(GLF_LFLUSH, &gl->gl_flags) && demote_ok(gl) &&
> +	    gl->gl_name.ln_type != LM_TYPE_RGRP)
>   		gfs2_glock_add_to_lru(gl);
>   
>   	trace_gfs2_glock_queue(gh, 0);
>



      reply	other threads:[~2015-06-15 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <512846443.16088997.1434133529467.JavaMail.zimbra@redhat.com>
2015-06-12 18:29 ` [Cluster-devel] [GFS2 PATCH] GFS2: Don't add rgrp glocks to the lru Bob Peterson
2015-06-15 11:19   ` 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=557EB4B1.9040000@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).