From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] ipv6 fib: Make rt6_info{} more cache-line aware.
Date: Thu, 01 Apr 2010 18:45:08 -0700 (PDT) [thread overview]
Message-ID: <20100401.184508.144448196.davem@davemloft.net> (raw)
In-Reply-To: <4BB45836.2060104@linux-ipv6.org>
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Date: Thu, 01 Apr 2010 17:24:22 +0900
> 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>
Applied.
prev parent reply other threads:[~2010-04-02 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 8:24 [PATCH net-next-2.6] ipv6 fib: Make rt6_info{} more cache-line aware YOSHIFUJI Hideaki
2010-04-02 1:45 ` David Miller [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=20100401.184508.144448196.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).