From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Eliminate __gfs2_glock_remove_from_lru
Date: Fri, 09 Jan 2015 16:49:19 +0000 [thread overview]
Message-ID: <54B0068F.9050201@redhat.com> (raw)
In-Reply-To: <896208988.3990696.1420482310095.JavaMail.zimbra@redhat.com>
Hi,
Now in the -nmw tree. Thanks,
Steve.
On 05/01/15 18:25, Bob Peterson wrote:
> Hi,
>
> Since the only caller of function __gfs2_glock_remove_from_lru locks the
> same spin_lock as gfs2_glock_remove_from_lru, the functions can be combined.
>
> Regards,
>
> Bob Peterson
> Red Hat File Systems
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> ---
> diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
> index a23524a..aeb7bc9 100644
> --- a/fs/gfs2/glock.c
> +++ b/fs/gfs2/glock.c
> @@ -173,19 +173,14 @@ void gfs2_glock_add_to_lru(struct gfs2_glock *gl)
> spin_unlock(&lru_lock);
> }
>
> -static void __gfs2_glock_remove_from_lru(struct gfs2_glock *gl)
> +static void gfs2_glock_remove_from_lru(struct gfs2_glock *gl)
> {
> + spin_lock(&lru_lock);
> if (!list_empty(&gl->gl_lru)) {
> list_del_init(&gl->gl_lru);
> atomic_dec(&lru_count);
> clear_bit(GLF_LRU, &gl->gl_flags);
> }
> -}
> -
> -static void gfs2_glock_remove_from_lru(struct gfs2_glock *gl)
> -{
> - spin_lock(&lru_lock);
> - __gfs2_glock_remove_from_lru(gl);
> spin_unlock(&lru_lock);
> }
>
> @@ -205,9 +200,7 @@ void gfs2_glock_put(struct gfs2_glock *gl)
>
> lockref_mark_dead(&gl->gl_lockref);
>
> - spin_lock(&lru_lock);
> - __gfs2_glock_remove_from_lru(gl);
> - spin_unlock(&lru_lock);
> + gfs2_glock_remove_from_lru(gl);
> spin_unlock(&gl->gl_lockref.lock);
> spin_lock_bucket(gl->gl_hash);
> hlist_bl_del_rcu(&gl->gl_list);
>
prev parent reply other threads:[~2015-01-09 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <652811562.3989950.1420482199546.JavaMail.zimbra@redhat.com>
2015-01-05 18:25 ` [Cluster-devel] [GFS2 PATCH] GFS2: Eliminate __gfs2_glock_remove_from_lru Bob Peterson
2015-01-09 16:49 ` 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=54B0068F.9050201@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).