From: Andrew Gallatin <gallatin@myri.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 2/3] myri10ge: Add vlan rx for better GRO perf.
Date: Wed, 14 Nov 2012 10:43:40 -0500 [thread overview]
Message-ID: <50A3BC2C.4000708@myri.com> (raw)
In-Reply-To: <1352904408.4497.11.camel@edumazet-glaptop>
On 11/14/12 09:46, Eric Dumazet wrote:
> On Wed, 2012-11-14 at 08:06 -0500, Andrew Gallatin wrote:
>>
>> Unlike LRO, GRO requires that vlan tags be removed before
>> aggregation can occur. Since the myri10ge NIC does not support
>> hardware vlan tag offload, we must remove the tag in the driver
>> to achieve performance comparable to LRO for vlan tagged frames.
>>
>> Signed-off-by: Andrew Gallatin <gallatin@myri.com>
>> ---
>> drivers/net/ethernet/myricom/myri10ge/myri10ge.c | 47
>> ++++++++++++++++++++++
>> 1 file changed, 47 insertions(+)
>>
>> diff --git a/drivers/net/ethernet/myricom/myri10ge/myri10ge.c
>> b/drivers/net/ethernet/myricom/myri10ge/myri10ge.c
>> index a5ab2f2..b9b6dfd 100644
>> --- a/drivers/net/ethernet/myricom/myri10ge/myri10ge.c
>> +++ b/drivers/net/ethernet/myricom/myri10ge/myri10ge.c
>> @@ -1264,6 +1264,48 @@ myri10ge_unmap_rx_page(struct pci_dev *pdev,
>> }
>> }
>>
>> +/*
>> + * GRO does not support acceleration of tagged vlan frames, and
>> + * this NIC does not support vlan tag offload, so we must pop
>> + * the tag ourselves to be able to achieve GRO performance that
>> + * is comparable to LRO.
>> + */
>> +
>> +static inline void
>> +myri10ge_vlan_rx(struct net_device *dev, void *addr, struct sk_buff *skb)
>> +{
>> + u8 *va;
>> + struct vlan_ethhdr *veh;
>> + struct ethhdr *eh;
>> + struct skb_frag_struct *frag;
>> + u16 proto;
>> +
>> + va = addr;
>> + va += MXGEFW_PAD;
>> + veh = (struct vlan_ethhdr *) va;
>> + if ((dev->features & (NETIF_F_HW_VLAN_RX | NETIF_F_GRO)) ==
>> + (NETIF_F_HW_VLAN_RX | NETIF_F_GRO) &&
>> + (veh->h_vlan_proto == ntohs(ETH_P_8021Q))) {
>> + /* fixup csum if needed */
>> + if (skb->ip_summed == CHECKSUM_COMPLETE)
>> + skb->csum = csum_sub(skb->csum,
>> + csum_partial(va + ETH_HLEN,
>> + VLAN_HLEN, 0));
>> + /* pop tag */
>> + __vlan_hwaccel_put_tag(skb, ntohs(veh->h_vlan_TCI));
>> + proto = veh->h_vlan_encapsulated_proto;
> I am not sure you need this @proto ?
>
>> + memmove(va + VLAN_HLEN, va, ETH_HLEN);
>
> You could only memmove the mac addresses (2 * ETH_ALEN)
> To not touch the proto (and avoid possible aliasing problems)
>
>> + va += VLAN_HLEN;
>> + eh = (struct ethhdr *)va;
>> + eh->h_proto = proto;
>
> and this should not be needed ?
Indeed, your suggestion works and is simpler and less risky.
Thank you for your help.
I also think that I am making a mistake by only popping the tag when
GRO is enabled. My fear is that something will become confused when
skb->dev->features contains NETIF_F_HW_VLAN_RX, but the tag is not
decap'ed. So I will remove the check for NETIF_F_GRO when popping
the vlan tag.
Thanks,
Drew
next prev parent reply other threads:[~2012-11-14 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 13:06 [PATCH net-next 2/3] myri10ge: Add vlan rx for better GRO perf Andrew Gallatin
2012-11-14 14:46 ` Eric Dumazet
2012-11-14 15:43 ` Andrew Gallatin [this message]
2012-11-14 16:32 ` [PATCH v2 " Andrew Gallatin
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=50A3BC2C.4000708@myri.com \
--to=gallatin@myri.com \
--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).