From: Eric Dumazet <dada1@cosmosbay.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [NETFILTER] xt_hashlimit : speedups hash_dst()
Date: Fri, 14 Dec 2007 22:37:15 +0100 [thread overview]
Message-ID: <4762F78B.80302@cosmosbay.com> (raw)
In-Reply-To: <4762EEB2.1080608@gmail.com>
Jarek Poplawski a écrit :
> Eric Dumazet wrote, On 12/14/2007 12:09 PM:
> ...
>
>> + /*
>> + * Instead of returning hash % ht->cfg.size (implying a divide)
>> + * we return the high 32 bits of the (hash * ht->cfg.size) that will
>> + * give results between [0 and cfg.size-1] and same hash distribution,
>> + * but using a multiply, less expensive than a divide
>> + */
>> + return ((u64)hash * ht->cfg.size) >> 32;
>
> Are we sure of the same hash distribution? Probably I miss something,
> but: if this 'hash' is well distributed on 32 bits, and ht->cfg.size
> is smaller than 32 bits, e.g. 256 (8 bits), then this multiplication
> moves to the higher 32 of u64 only max. 8 bits of the most significant
> byte, and the other three bytes are never used, while division is
> always affected by all four bytes...
Not sure what you are saying... but if size=256, then, yes, we want a final
result between 0 and 255, so three bytes are nul.
'size' is the size of hashtable, its not a random 32bits value :)
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-12-14 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 11:09 [NETFILTER] xt_hashlimit : speedups hash_dst() Eric Dumazet
2007-12-14 11:20 ` Patrick McHardy
2007-12-14 18:30 ` David Miller
2007-12-14 20:59 ` Jarek Poplawski
2007-12-14 21:37 ` Eric Dumazet [this message]
2007-12-15 10:41 ` Jarek Poplawski
2007-12-15 11:04 ` Eric Dumazet
2007-12-16 5:42 ` David Miller
2007-12-17 12:38 ` Patrick McHardy
2007-12-17 14:04 ` Sami Farin
2007-12-17 14:15 ` Patrick McHardy
2007-12-14 21:40 ` Jarek Poplawski
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=4762F78B.80302@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=jarkao2@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.