From: Jeff Layton <jlayton@redhat.com>
To: Frank Sorenson <sorenson@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] sunrpc: include gid in the rpc_cred_cache hash
Date: Fri, 16 Sep 2016 16:42:15 -0400 [thread overview]
Message-ID: <1474058535.13386.6.camel@redhat.com> (raw)
In-Reply-To: <1474056735-4008-1-git-send-email-sorenson@redhat.com>
On Fri, 2016-09-16 at 15:12 -0500, Frank Sorenson wrote:
> The current rpc_cred_cache hashtable uses only the uid in the hash
> computation. rpc_creds created with the same uid but different
> gids will all go on the same hash chain.
>
> In certain usage patterns, such as the following, this can lead to
> extremely long hash chains for these uids, while the rest of the
> hashtable remains nearly empty. This causes very high cpu usage
> in rpcauth_lookup_credcache, and slow performance for that uid.
>
> for (i = 0 ; i < 100000 ; i++) {
> setregid(-1, i);
> stat(path, &st);
> }
>
> Add the gid to the hash algorithm to distribute the rpc_creds
> throughout the cache to avoid long individual hash chains.
>
> > Signed-off-by: Frank Sorenson <sorenson@redhat.com>
>
> diff --git a/net/sunrpc/auth.c b/net/sunrpc/auth.c
> index a7e42f9..2260e58 100644
> --- a/net/sunrpc/auth.c
> +++ b/net/sunrpc/auth.c
> @@ -538,6 +538,14 @@ rpcauth_cache_enforce_limit(void)
> > rpcauth_cache_do_shrink(nr_to_scan);
> }
>
> +static unsigned int
> +rpcauth_hash_acred(struct auth_cred *acred, unsigned int hashbits)
> +{
> > + return hash_64(from_kgid(&init_user_ns, acred->gid) |
> > + (from_kuid(&init_user_ns, acred->uid) << (sizeof(gid_t) * 8)),
> > + hashbits);
> +}
> +
> /*
> * Look up a process' credentials in the authentication cache
> */
> @@ -551,7 +559,7 @@ rpcauth_lookup_credcache(struct rpc_auth *auth, struct auth_cred * acred,
> > *entry, *new;
> > unsigned int nr;
>
> > - nr = hash_long(from_kuid(&init_user_ns, acred->uid), cache->hashbits);
> > + nr = rpcauth_hash_acred(acred, cache->hashbits);
>
> > rcu_read_lock();
> > hlist_for_each_entry_rcu(entry, &cache->hashtable[nr], cr_hash) {
>
Nice work.
Reviewed-by: Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2016-09-16 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 20:12 [PATCH] sunrpc: include gid in the rpc_cred_cache hash Frank Sorenson
2016-09-16 20:42 ` Jeff Layton [this message]
2016-09-16 21:10 ` kbuild test robot
2016-09-16 21:37 ` Trond Myklebust
2016-09-19 13:10 ` Frank Sorenson
2016-09-19 14:49 ` Trond Myklebust
2016-09-19 15:37 ` Frank Sorenson
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=1474058535.13386.6.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sorenson@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).