From: Chas Williams <3chas3@gmail.com>
To: jerry.lilijun@huawei.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] bonding: add QinQ packet xmit hash support
Date: Sun, 16 Sep 2018 12:02:24 -0400 [thread overview]
Message-ID: <CAG2-Gkk_4+6am7gLhzqxRB7Z02RrQM5aJgUM6Sii7PL8C7SJbQ@mail.gmail.com> (raw)
In-Reply-To: <1536976343-5548-1-git-send-email-jerry.lilijun@huawei.com>
I think this change already went in dpdk-next-net:
commit 61e99d7e944885e8d625ded41b5877653e0b637e
Author: Yunjian Wang <wangyunjian@huawei.com>
Date: Tue Aug 7 16:10:46 2018 +0800
net/bonding: add support to match on 0x88A8 ethertype
We assume VLAN ethtertype is 0x8100 in get_vlan_offset() function,
but it could be 0x88A8 if QinQ is supported.
Fixes: 06fe78b98ccd ("bond: add mode 6")
Cc: stable@dpdk.org
Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
Acked-by: Chas Williams <chas3@att.com>
On Fri, Sep 14, 2018 at 9:52 PM Lilijun <jerry.lilijun@huawei.com> wrote:
>
> For QinQ packet with ether type 0x88a8, dpdk bond's xmit hash policy is
> not worked to get the ip or port field.
>
> Signed-off-by: Lilijun <jerry.lilijun@huawei.com>
> ---
> drivers/net/bonding/rte_eth_bond_pmd.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c b/drivers/net/bonding/rte_eth_bond_pmd.c
> index 58f7377..4417422 100644
> --- a/drivers/net/bonding/rte_eth_bond_pmd.c
> +++ b/drivers/net/bonding/rte_eth_bond_pmd.c
> @@ -37,7 +37,8 @@
> {
> size_t vlan_offset = 0;
>
> - if (rte_cpu_to_be_16(ETHER_TYPE_VLAN) == *proto) {
> + if (rte_cpu_to_be_16(ETHER_TYPE_VLAN) == *proto ||
> + rte_cpu_to_be_16(ETHER_TYPE_QINQ) == *proto) {
> struct vlan_hdr *vlan_hdr = (struct vlan_hdr *)(eth_hdr + 1);
>
> vlan_offset = sizeof(struct vlan_hdr);
> --
> 1.8.4.msysgit.0
>
>
next prev parent reply other threads:[~2018-09-16 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 1:52 Lilijun
2018-09-16 16:02 ` Chas Williams [this message]
2018-09-17 3:25 ` Lilijun (Jerry, Cloud Networking)
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=CAG2-Gkk_4+6am7gLhzqxRB7Z02RrQM5aJgUM6Sii7PL8C7SJbQ@mail.gmail.com \
--to=3chas3@gmail.com \
--cc=dev@dpdk.org \
--cc=jerry.lilijun@huawei.com \
/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).