From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sowmini Varadhan Subject: Re: [RFC] Kernel unaligned access at __skb_flow_dissect Date: Fri, 29 Jan 2016 18:58:00 -0500 Message-ID: <20160129235800.GH17127@oracle.com> References: <20160129180651.GA17127@oracle.com> <1454092428.7627.52.camel@edumazet-glaptop2.roam.corp.google.com> <1454093642.7627.57.camel@edumazet-glaptop2.roam.corp.google.com> <20160129210900.GD17127@oracle.com> <20160129230424.GG17127@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Eric Dumazet , Michael Dalton , Linux Kernel Network Developers To: Tom Herbert Return-path: Received: from userp1040.oracle.com ([156.151.31.81]:27567 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753688AbcA2X6P (ORCPT ); Fri, 29 Jan 2016 18:58:15 -0500 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On (01/29/16 15:31), Tom Herbert wrote: > But even within flow dissector, to be completely correct, we need to > replace all 32-bit accesses with the mempy (flow_label, mpls label, > keyid) and be vigilant about new ones coming in. For that matter, .. well, one question that came to my mind when I was looking at this is: why does eth_get_headlen try to compute the flow hash even before the driver has had a chance to pull things into an aligned buffer? Isn't that just risking even more unaligned accesses?