From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] route: fix breakage after moving lwtunnel state Date: Sun, 23 Aug 2015 16:51:03 -0700 (PDT) Message-ID: <20150823.165103.2104601245219561984.davem@davemloft.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: jbenc@redhat.com Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:47198 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753356AbbHWXvE (ORCPT ); Sun, 23 Aug 2015 19:51:04 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Jiri Benc Date: Fri, 21 Aug 2015 12:41:14 +0200 > @@ -99,6 +99,9 @@ struct dst_entry { > atomic_t __refcnt; /* client references */ > int __use; > unsigned long lastuse; > +#ifndef CONFIG_64BIT > + struct lwtunnel_state *lwtstate; > +#endif > union { > struct dst_entry *next; > struct rtable __rcu *rt_next; I'm going to apply this to fix the build error without reverting your change entirely, but this is really an undesirable solution. This cache line of the SKB is for write heavy members of struct dst_entry and so if you put a read-mostly member here it's going to result in performance problems.