From: Eric Dumazet <eric.dumazet@gmail.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: David Miller <davem@davemloft.net>,
mingo@elte.hu, paulmck@linux.vnet.ibm.com,
cl@linux-foundation.org, penberg@kernel.org, mpm@selenic.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 4/4 V2] net,rcu: don't assume the size of struct rcu_head
Date: Tue, 01 Mar 2011 10:20:13 +0100 [thread overview]
Message-ID: <1298971213.3284.4.camel@edumazet-laptop> (raw)
In-Reply-To: <4D6CB414.8050107@cn.fujitsu.com>
Le mardi 01 mars 2011 A 16:53 +0800, Lai Jiangshan a A(C)crit :
> On 03/01/2011 04:16 PM, David Miller wrote:
> > From: Lai Jiangshan <laijs@cn.fujitsu.com>
> > Date: Tue, 01 Mar 2011 16:03:44 +0800
> >
> >>
> >> struct dst_entry assumes the size of struct rcu_head as 2 * sizeof(long)
> >> and manually adds pads for aligning for "__refcnt".
> >>
> >> When the size of struct rcu_head is changed, these manual padding
> >> is wrong. Use __attribute__((aligned (64))) instead.
> >>
> >> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> >
> > We don't want to use the align if it's going to waste lots of space.
> >
> > Instead we want to rearrange the structure so that the alignment comes
> > more cheaply.
>
> Subject: [PATCH 4/4 V2] net,rcu: don't assume the size of struct rcu_head
>
> struct dst_entry assumes the size of struct rcu_head as 2 * sizeof(long)
> and manually adds pads for aligning for "__refcnt".
>
> When the size of struct rcu_head is changed, these manual padding
> are hardly suit for the changes. So we rearrange the structure,
> and move the seldom access rcu_head to the end of the structure.
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
>
> diff --git a/include/net/dst.h b/include/net/dst.h
> index 93b0310..d8c5296 100644
> --- a/include/net/dst.h
> +++ b/include/net/dst.h
> @@ -37,7 +37,6 @@
> struct sk_buff;
>
> struct dst_entry {
> - struct rcu_head rcu_head;
> struct dst_entry *child;
> struct net_device *dev;
> short error;
> @@ -78,6 +77,13 @@ struct dst_entry {
> __u32 __pad2;
> #endif
>
> + unsigned long lastuse;
> + union {
> + struct dst_entry *next;
> + struct rtable __rcu *rt_next;
> + struct rt6_info *rt6_next;
> + struct dn_route __rcu *dn_next;
> + };
>
> /*
> * Align __refcnt to a 64 bytes alignment
> @@ -92,13 +98,7 @@ struct dst_entry {
> */
> atomic_t __refcnt; /* client references */
> int __use;
> - unsigned long lastuse;
> - union {
> - struct dst_entry *next;
> - struct rtable __rcu *rt_next;
> - struct rt6_info *rt6_next;
> - struct dn_route __rcu *dn_next;
> - };
> + struct rcu_head rcu_head;
> };
>
> #ifdef __KERNEL__
Nope...
"lastuse" and "next" must be in this place, or this introduce false
sharing we wanted to avoid in the past.
I suggest you leave this code as is, we will address the problem when
rcu_head changes (assuming we can test a CONFIG_RCU_HEAD_DEBUG or
something)
First part of "struct dst_entry" is mostly read, while part beginning
after refcnt is often written.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-01 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 8:03 [PATCH 4/4] " Lai Jiangshan
2011-03-01 8:16 ` David Miller
2011-03-01 8:20 ` Eric Dumazet
2011-03-01 8:53 ` [PATCH 4/4 V2] " Lai Jiangshan
2011-03-01 9:20 ` Eric Dumazet [this message]
2011-03-02 2:46 ` Lai Jiangshan
2011-03-02 3:02 ` Eric Dumazet
2011-03-01 8:20 ` [PATCH 4/4] " Eric Dumazet
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=1298971213.3284.4.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=cl@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox