linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.com>
Cc: NFS List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] sunrpc: remove 'inuse' flag from struct cache_detail.
Date: Thu, 2 Jun 2016 16:31:06 -0400	[thread overview]
Message-ID: <20160602203106.GB15621@fieldses.org> (raw)
In-Reply-To: <87inxsp0ew.fsf@notabene.neil.brown.name>

On Thu, Jun 02, 2016 at 04:31:03PM +1000, NeilBrown wrote:
> 
> This field is not currently in use.

Hah.  OK, thanks.--b.

> 
> Signed-off-by: NeilBrown <neilb@suse.com>
> ---
> 
> I recently noticed this and wondered what it was for. "Nothing" seems to
> be the answer..
> 
> NeilBrown
> 
> 
>  include/linux/sunrpc/cache.h | 2 --
>  net/sunrpc/cache.c           | 2 +-
>  2 files changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/include/linux/sunrpc/cache.h b/include/linux/sunrpc/cache.h
> index ed03c9f7f908..62a60eeacb0a 100644
> --- a/include/linux/sunrpc/cache.h
> +++ b/include/linux/sunrpc/cache.h
> @@ -78,8 +78,6 @@ struct cache_detail {
>  	struct hlist_head *	hash_table;
>  	rwlock_t		hash_lock;
>  
> -	atomic_t		inuse; /* active user-space update or lookup */
> -
>  	char			*name;
>  	void			(*cache_put)(struct kref *);
>  
> diff --git a/net/sunrpc/cache.c b/net/sunrpc/cache.c
> index 553bf95f7003..4d8e11f94a35 100644
> --- a/net/sunrpc/cache.c
> +++ b/net/sunrpc/cache.c
> @@ -362,7 +362,7 @@ void sunrpc_destroy_cache_detail(struct cache_detail *cd)
>  	cache_purge(cd);
>  	spin_lock(&cache_list_lock);
>  	write_lock(&cd->hash_lock);
> -	if (cd->entries || atomic_read(&cd->inuse)) {
> +	if (cd->entries) {
>  		write_unlock(&cd->hash_lock);
>  		spin_unlock(&cache_list_lock);
>  		goto out;
> -- 
> 2.8.3
> 



      reply	other threads:[~2016-06-02 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02  6:31 [PATCH] sunrpc: remove 'inuse' flag from struct cache_detail NeilBrown
2016-06-02 20:31 ` J. Bruce Fields [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=20160602203106.GB15621@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.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).