From: Alexander Duyck <alexander.h.duyck@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
David Miller <davem@davemloft.net>,
"alexander.duyck@gmail.com" <alexander.duyck@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] flow-dissector: Fix alignment issue in __skb_flow_get_ports
Date: Fri, 10 Oct 2014 09:50:17 -0700 [thread overview]
Message-ID: <54380E49.5050504@redhat.com> (raw)
In-Reply-To: <1412954973.9362.11.camel@edumazet-glaptop2.roam.corp.google.com>
On 10/10/2014 08:29 AM, Eric Dumazet wrote:
> On Fri, 2014-10-10 at 08:14 -0700, Alexander Duyck wrote:
>
>> I think you might be coming to this a little late. The igb and ixgbe
>> drivers had been working this way for a long time. We did a memcpy to
>> move the headers from the page and into the skb->data at an aligned
>> offset. In order to determine the length to memcpy we had a function
>> that could walk through the DMA aligned data to get the header length.
>> The function for that was replaced with the __skb_flow_dissect as it was
>> considered a duplication of code with the flow_dissection functions.
>> However that is obviously not the case now that we are hitting these
>> alignment issues.
>>
>> The question I have in all this is do I push forward and make
>> __skb_flow_dissect work with unaligned accesses, or do I back off and
>> put something equivilent to igb/ixgbe_get_headlen functions in the
>> kernel in order to deal with the unaligned accesses as they had no
>> issues with them since they were only concerned with getting the header
>> length and kept all accesses 16b aligned.
>>
> I see nothing wrong dealing with unaligned accesses, as these helpers
> are nop on x86 or CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y arches.
Still it means possibly hurting performance on those platforms that
don't have it defined.
If I just use get_unaligned that is pretty easy in terms of cleanup for
the ports and IPv4 addresses, the IPv6 will still be a significant
hurdle to overcome though.
Thanks,
Alex
next prev parent reply other threads:[~2014-10-10 16:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 0:12 eth_get_headlen() and unaligned accesses David Miller
2014-10-10 3:10 ` Alexander Duyck
2014-10-10 4:43 ` David Miller
2014-10-10 10:59 ` David Laight
2014-10-10 4:03 ` [PATCH] flow-dissector: Fix alignment issue in __skb_flow_get_ports alexander.duyck
2014-10-10 4:47 ` David Miller
2014-10-10 14:42 ` Alexander Duyck
2014-10-10 14:57 ` David Laight
2014-10-10 15:14 ` Alexander Duyck
2014-10-10 15:29 ` Eric Dumazet
2014-10-10 16:50 ` Alexander Duyck [this message]
2014-10-10 17:58 ` David Miller
2014-10-10 18:02 ` Alexander Duyck
2014-10-10 18:14 ` David Miller
2014-10-10 18:15 ` David Miller
2014-10-10 18:22 ` David Miller
2014-10-10 18:53 ` Alexander Duyck
2014-10-10 19:32 ` David Miller
2014-10-13 8:32 ` David Laight
2014-10-10 15:33 ` Eric Dumazet
2014-10-10 16:30 ` David Laight
2014-10-10 16:41 ` David Miller
2014-10-10 14:59 ` [PATCH v2] " alexander.duyck
2014-10-10 15:36 ` Eric Dumazet
2014-10-10 17:55 ` David Miller
2014-10-10 18:41 ` eth_get_headlen() and unaligned accesses Tom Herbert
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=54380E49.5050504@redhat.com \
--to=alexander.h.duyck@redhat.com \
--cc=David.Laight@ACULAB.COM \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).