From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Tue, 6 Nov 2012 02:58:54 +0800 References: <1351982508-16991-1-git-send-email-sven@narfation.org> In-Reply-To: <1351982508-16991-1-git-send-email-sven@narfation.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201211060258.54459.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] [RFC] batman-adv: Reorder structs to reduce padding Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking On Sunday, November 04, 2012 06:41:48 Sven Eckelmann wrote: > - struct batadv_neigh_node __rcu *router; /* rcu protected pointer */ > #ifdef CONFIG_BATMAN_ADV_DAT > batadv_dat_addr_t dat_addr; > #endif > + uint8_t flags; > + uint8_t gw_flags; > + struct batadv_neigh_node __rcu *router; /* rcu protected pointer */ Shouldn't we move batadv_dat_addr_t to the end of the struct to achieve the smallest possible struct regardless of whether DAT is compiled in or not ? Or does it have no effect ? Cheers, Marek