From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Linus Torvalds <torvalds@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 2/2] The new jhash implementation
Date: Thu, 25 Nov 2010 18:21:09 +0100 [thread overview]
Message-ID: <1290705669.2858.381.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1011251520270.1198@blackhole.kfki.hu>
Le jeudi 25 novembre 2010 à 15:41 +0100, Jozsef Kadlecsik a écrit :
...
> +/* __jhash_mix -- mix 3 32-bit values reversibly. */
> +#define __jhash_mix(a, b, c) \
> +{ \
> + a -= c; a ^= rol32(c, 4); c += b; \
> + b -= a; b ^= rol32(a, 6); a += c; \
> + c -= b; c ^= rol32(b, 8); b += a; \
> + a -= c; a ^= rol32(c, 16); c += b; \
> + b -= a; b ^= rol32(a, 19); a += c; \
> + c -= b; c ^= rol32(b, 4); b += a; \
> +}
> +
> +/* __jhash_final - final mixing of 3 32-bit values (a,b,c) into c */
> +#define __jhash_final(a, b, c) \
> +{ \
> + c ^= b; c -= rol32(b, 14); \
> + a ^= c; a -= rol32(c, 11); \
> + b ^= a; b -= rol32(a, 25); \
> + c ^= b; c -= rol32(b, 16); \
> + a ^= c; a -= rol32(c, 4); \
> + b ^= a; b -= rol32(a, 14); \
> + c ^= b; c -= rol32(b, 24); \
> +}
> +
So we now have a special __jhash_final(a, b, c) thing for the last
values.
> +/* jhash_3words - hash exactly 3, 2 or 1 word(s) */
> +u32 jhash_3words(u32 a, u32 b, u32 c, u32 initval)
> +{
> + a += JHASH_INITVAL;
> + b += JHASH_INITVAL;
> + c += initval;
> +
> + __jhash_mix(a, b, c);
> +
> + return c;
> +}
> +EXPORT_SYMBOL(jhash_3words);
But you dont use it in jhash_3words().
I do think jhash_3words() should stay inlined, unless maybe
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
We hit it several time per packet in network stack in RX path.
Once in skb_get_rxhash() (unless device fills skb->rxhash)
Once at least in conntrack (if used).
Once in UDP or TCP stack
--
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:[~2010-11-25 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 13:15 [PATCH 0/2] New jhash function Jozsef Kadlecsik
2010-11-25 13:15 ` [PATCH 1/2] Prepare the tree for un-inlined jhash Jozsef Kadlecsik
2010-11-25 13:15 ` [PATCH 2/2] The new jhash implementation Jozsef Kadlecsik
2010-11-25 13:49 ` Eric Dumazet
2010-11-25 13:55 ` Changli Gao
2010-11-25 14:05 ` Eric Dumazet
2010-11-25 14:41 ` Jozsef Kadlecsik
2010-11-25 17:21 ` Eric Dumazet [this message]
2010-11-25 21:14 ` Jozsef Kadlecsik
2010-11-27 3:31 ` Rusty Russell
2010-12-03 12:38 ` [PATCH 0/2] New jhash function Jozsef Kadlecsik
2010-12-03 12:39 ` [PATCH 1/2] Remove calls to jhash internals Jozsef Kadlecsik
2010-12-03 12:39 ` [PATCH 2/2] The new jhash implementation Jozsef Kadlecsik
2010-12-08 17:09 ` [PATCH 0/2] New jhash function David Miller
2010-12-08 21:23 ` Rusty Russell
2010-12-10 4:19 ` David Miller
2010-11-25 13:39 ` [PATCH 1/2] Prepare the tree for un-inlined jhash Jan Engelhardt
2010-11-25 13:57 ` Jozsef Kadlecsik
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=1290705669.2858.381.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox