| commit | bd2c77a0a749589b45f2697ea446a4438d078f9b | |
| author | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org> | |
| Wed, 31 Mar 2010 22:24:22 +0000 (31 22:24 +0000) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Fri, 2 Apr 2010 01:41:41 +0000 (1 18:41 -0700) | ||
| tree | 801d2f87cad4bd6bafd946ad4eb16cb1c0db779b | treesnapshot (tar.gz zip) |
| parent | 152102c7f2bf191690f1069bae292ea3925adf14 | commitdiff |
ipv6 fib: Make rt6_info{} more cache-line aware.
The head element of rt6_info{} is dst_entry{}, and
IPv6 specific elements follow.
Because elements at the end of dst_entry{} are frequently
updated, it is not good to put frequently-used static
elements, such as rt6i_idev, rt6i_dst or rt6i_flags in the
same cache line.
On the other hand, fib6_table, rt6i_node or rt6i_gateway are
rarely used, so it is okay to stay in the same cache line.
Let's rearrange rt6_info{}.
Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
The head element of rt6_info{} is dst_entry{}, and
IPv6 specific elements follow.
Because elements at the end of dst_entry{} are frequently
updated, it is not good to put frequently-used static
elements, such as rt6i_idev, rt6i_dst or rt6i_flags in the
same cache line.
On the other hand, fib6_table, rt6i_node or rt6i_gateway are
rarely used, so it is okay to stay in the same cache line.
Let's rearrange rt6_info{}.
Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
| include/net/ip6_fib.h | diffblobblamehistory |