From: Eric Dumazet <dada1@cosmosbay.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH 3/6] IPV4 : use xor rather than multiple ands for route compare
Date: Tue, 01 Apr 2008 07:52:03 +0200 [thread overview]
Message-ID: <47F1CD83.8090905@cosmosbay.com> (raw)
In-Reply-To: <20080401004724.601457403@vyatta.com>
Stephen Hemminger a écrit :
> The comparison in ip_route_input is a hot path, by recoding the C
> "and" as bit operations, fewer conditional branches get generated
> so the code should be faster. Maybe someday Gcc will be smart
> enough to do this?
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
>
> --- a/net/ipv4/route.c 2008-03-31 10:57:30.000000000 -0700
> +++ b/net/ipv4/route.c 2008-03-31 11:10:44.000000000 -0700
> @@ -2079,14 +2079,14 @@ int ip_route_input(struct sk_buff *skb,
> rcu_read_lock();
> for (rth = rcu_dereference(rt_hash_table[hash].chain); rth;
> rth = rcu_dereference(rth->u.dst.rt_next)) {
> - if (rth->fl.fl4_dst == daddr &&
> - rth->fl.fl4_src == saddr &&
> - rth->fl.iif == iif &&
> - rth->fl.oif == 0 &&
> - rth->fl.mark == skb->mark &&
> - rth->fl.fl4_tos == tos &&
> - net_eq(dev_net(rth->u.dst.dev), net) &&
> - rth->rt_genid == atomic_read(&rt_genid)) {
> + if (((rth->fl.fl4_dst ^ daddr) |
> + (rth->fl.fl4_src ^ saddr) |
> + (rth->fl.iif ^ iif) |
> + rth->fl.oif |
> + (rth->fl.mark ^ skb->mark) |
> + (rth->fl.fl4_tos ^ tos) |
> + (rth->rt_genid ^ atomic_read(&rt_genid))) == 0 &&
> + net_eq(dev_net(rth->u.dst.dev), net)) {
> dst_use(&rth->u.dst, jiffies);
> RT_CACHE_STAT_INC(in_hit);
> rcu_read_unlock();
>
Are you sure all fields share same cache lines, on 32bit and 64bit arches ?
I prefer having some conditional branches instead of cache misses, given that
the first two branches are usually discriminant.
Maybe we could let one test on (daddr,saddr) to do a fast segregation (with
one cache line at most) of candidates, then one remaining compare on other keys ?
next prev parent reply other threads:[~2008-04-01 5:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080401004708.009204033@vyatta.com>
2008-04-01 0:47 ` [PATCH 1/6] socket: sk_filter minor cleanups Stephen Hemminger
2008-04-10 8:39 ` David Miller
2008-04-01 0:47 ` [PATCH 2/6] socket: sk_filter deinline Stephen Hemminger
2008-04-10 8:49 ` David Miller
2008-04-01 0:47 ` [PATCH 3/6] IPV4 : use xor rather than multiple ands for route compare Stephen Hemminger
2008-04-01 5:52 ` Eric Dumazet [this message]
2008-04-01 20:08 ` Stephen Hemminger
2008-04-10 8:51 ` David Miller
2008-04-10 9:01 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-10 10:56 ` David Miller
2008-04-10 12:17 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-10 9:26 ` Eric Dumazet
2008-04-10 11:00 ` David Miller
2008-04-01 0:47 ` [PATCH 4/6] IPV4: route inline changes Stephen Hemminger
2008-04-10 8:53 ` David Miller
2008-04-01 0:47 ` [PATCH 5/6] IPV4: route use jhash3 Stephen Hemminger
2008-04-10 8:54 ` David Miller
2008-04-01 0:47 ` [PATCH 6/6] IPV4: route rekey timer can be deferrable Stephen Hemminger
2008-04-10 8:55 ` David Miller
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=47F1CD83.8090905@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 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.