From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux@sciencehorizons.net
Cc: jlayton@poochiereds.net, linux-nfs@vger.kernel.org
Subject: Re: [PATCH RESEND 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hash_string()
Date: Thu, 26 May 2016 14:45:42 -0400 [thread overview]
Message-ID: <20160526184542.GC22868@fieldses.org> (raw)
In-Reply-To: <20160526183939.30389.qmail@ns.sciencehorizons.net>
On Thu, May 26, 2016 at 02:39:39PM -0400, George Spelvin wrote:
> Finally, the first use of previous two patches: Eliminate the
> separate ad-hoc string hash functions in the sunrpc code.
>
> This also eliminates the only caller of hash_long which asks for
> more than 32 bits of output.
>
> sunrpc guys: Is it okay if I send this to Linus directly?
Sorry for ignoring this.... Looks straightforward to me; for what it's
worth:
Acked-by: J. Bruce Fields <bfields@redhat.com>
If you have a git branch I could fetch, I could also run my usual tests
on it. (Which would only help in the unlikely case this breaks nfs
completely somehow--they certainly wouldn't catch some hash performance
regressoin.)
--b.
>
> Signed-off-by: George Spelvin <linux@sciencehorizons.net>
> Cc: "J. Bruce Fields" <bfields@fieldses.org>
> Cc: Jeff Layton <jlayton@poochiereds.net>
> Cc: linux-nfs@vger.kernel.org
> ---
> I have't heard anything from the linix-NFS crowd, so this is a re-ping.
>
> I've been having some e-mail troubles leading to increased spam scores
> due to a recent domain name change, so this is a resend from a different
> address in case the previous copy got binned.
>
> I'll happily send along the entire patch series, but the tl;dr is this
> is part of a patch series that improves the <linux/hash.h> and fs/namei.c
> hash functions, implementing Linus's suggestion:
>
> On Mon, 02 May 2016 at 09:24:21, Linus Torvalds wrote:
> > That said, I actually think hash_str() should be killed entirely.
> > Better just use what we use for pathnames: full_name_hash() (which
> > gets a pointer and length) and hash_name (which gets the string).
> >
> > Those functions do the "word-at-a-time" optimization, and they should
> > do a good enough job. If they aren't, we should fix them, because they
> > are a hell of a lot more important than anything that the svcauth code
> > does.
>
> He had a typically fulminating comment about the hard-to-predict if()
> branch in the inner loop.
>
> include/linux/sunrpc/svcauth.h | 36 +++++-------------------------------
> 1 file changed, 5 insertions(+), 31 deletions(-)
>
> diff --git a/include/linux/sunrpc/svcauth.h b/include/linux/sunrpc/svcauth.h
> index c00f53a4..ef2b2552 100644
> --- a/include/linux/sunrpc/svcauth.h
> +++ b/include/linux/sunrpc/svcauth.h
> @@ -16,6 +16,7 @@
> #include <linux/sunrpc/cache.h>
> #include <linux/sunrpc/gss_api.h>
> #include <linux/hash.h>
> +#include <linux/stringhash.h>
> #include <linux/cred.h>
>
> struct svc_cred {
> @@ -165,41 +166,14 @@ extern int svcauth_unix_set_client(struct svc_rqst *rqstp);
> extern int unix_gid_cache_create(struct net *net);
> extern void unix_gid_cache_destroy(struct net *net);
>
> -static inline unsigned long hash_str(char *name, int bits)
> +static inline unsigned long hash_str(char const *name, int bits)
> {
> - unsigned long hash = 0;
> - unsigned long l = 0;
> - int len = 0;
> - unsigned char c;
> - do {
> - if (unlikely(!(c = *name++))) {
> - c = (char)len; len = -1;
> - }
> - l = (l << 8) | c;
> - len++;
> - if ((len & (BITS_PER_LONG/8-1))==0)
> - hash = hash_long(hash^l, BITS_PER_LONG);
> - } while (len);
> - return hash >> (BITS_PER_LONG - bits);
> + return hash_32(hashlen_hash(hash_string(name)), bits);
> }
>
> -static inline unsigned long hash_mem(char *buf, int length, int bits)
> +static inline unsigned long hash_mem(char const *buf, int length, int bits)
> {
> - unsigned long hash = 0;
> - unsigned long l = 0;
> - int len = 0;
> - unsigned char c;
> - do {
> - if (len == length) {
> - c = (char)len; len = -1;
> - } else
> - c = *buf++;
> - l = (l << 8) | c;
> - len++;
> - if ((len & (BITS_PER_LONG/8-1))==0)
> - hash = hash_long(hash^l, BITS_PER_LONG);
> - } while (len);
> - return hash >> (BITS_PER_LONG - bits);
> + return hash_32(full_name_hash(buf, length), bits);
> }
>
> #endif /* __KERNEL__ */
> --
> 2.8.1
>
next prev parent reply other threads:[~2016-05-26 18:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+55aFxPSW+84KfQ1N_WmND-wtvgj2zQm8nFPkRcc+gyU=uing@mail.gmail.com>
2016-05-25 7:20 ` [PATCH 00/10] String hash improvements George Spelvin
2016-05-25 8:00 ` Geert Uytterhoeven
2016-05-25 8:11 ` George Spelvin
2016-05-25 8:50 ` Geert Uytterhoeven
2016-05-25 9:07 ` George Spelvin
2016-05-25 16:08 ` Linus Torvalds
[not found] ` <1464465443-25305-1-git-send-email-linux@sciencehorizons.net>
2016-05-28 19:57 ` [PATCH v3 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hashlen_string() George Spelvin
2016-06-02 22:59 ` [PATCH 00/10] String hash improvements Fubo Chen
2016-05-25 7:26 ` [PATCH 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hash_string() George Spelvin
2016-05-26 18:39 ` [PATCH RESEND " George Spelvin
2016-05-26 18:45 ` J. Bruce Fields [this message]
[not found] <20160527003254.GA25272@fieldses.org>
2016-05-27 1:56 ` George Spelvin
2016-05-27 3:29 ` George Spelvin
2016-05-27 12:16 ` J. Bruce Fields
2016-05-27 12:20 ` George Spelvin
2016-05-27 17:40 ` J. Bruce Fields
2016-05-27 21:25 ` George Spelvin
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=20160526184542.GC22868@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@sciencehorizons.net \
/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).