linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: akpm@linux-foundation.org, jack@suse.cz,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	a.ryabinin@samsung.com
Subject: Re: [PATCH] fs, jbd: use a more generic hash function
Date: Wed, 22 Oct 2014 10:02:18 +0200	[thread overview]
Message-ID: <20141022080218.GA26827@quack.suse.cz> (raw)
In-Reply-To: <1413924235-26276-1-git-send-email-sasha.levin@oracle.com>

On Tue 21-10-14 16:43:55, Sasha Levin wrote:
> While the hash function used by the revoke hashtable is good somewhere else,
> it's not really good here.
> 
> The default hash shift (8) means that one third of the hashing function
> gets lost (and is undefined anyways (8 - 12 = negative shift)):
> 
> 	"(block << (hash_shift - 12))) & (table->hash_size - 1)"
> 
> Instead, just use the kernel's generic hash function that gets used everywhere
> else.
  Thanks. Merged to my tree.

								Honza
> 
> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
> ---
>  fs/jbd/revoke.c |    7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/jbd/revoke.c b/fs/jbd/revoke.c
> index 8898bbd..dcead63 100644
> --- a/fs/jbd/revoke.c
> +++ b/fs/jbd/revoke.c
> @@ -93,6 +93,7 @@
>  #include <linux/bio.h>
>  #endif
>  #include <linux/log2.h>
> +#include <linux/hash.h>
>  
>  static struct kmem_cache *revoke_record_cache;
>  static struct kmem_cache *revoke_table_cache;
> @@ -129,15 +130,11 @@ static void flush_descriptor(journal_t *, struct journal_head *, int, int);
>  
>  /* Utility functions to maintain the revoke table */
>  
> -/* Borrowed from buffer.c: this is a tried and tested block hash function */
>  static inline int hash(journal_t *journal, unsigned int block)
>  {
>  	struct jbd_revoke_table_s *table = journal->j_revoke;
> -	int hash_shift = table->hash_shift;
>  
> -	return ((block << (hash_shift - 6)) ^
> -		(block >> 13) ^
> -		(block << (hash_shift - 12))) & (table->hash_size - 1);
> +	return hash_32(block, table->hash_shift);
>  }
>  
>  static int insert_revoke_hash(journal_t *journal, unsigned int blocknr,
> -- 
> 1.7.10.4
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2014-10-22  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 20:43 [PATCH] fs, jbd: use a more generic hash function Sasha Levin
2014-10-22  8:02 ` Jan Kara [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=20141022080218.GA26827@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=a.ryabinin@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sasha.levin@oracle.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).