From: Veaceslav Falico <vfalico@redhat.com>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
andy@greyhouse.net, kaber@trash.net, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/3] bonding: support QinQ for bond arp interval
Date: Wed, 19 Mar 2014 06:39:58 +0100 [thread overview]
Message-ID: <20140319053958.GA1242@redhat.com> (raw)
In-Reply-To: <5328F2F5.6010304@huawei.com>
On Wed, Mar 19, 2014 at 09:29:25AM +0800, Ding Tianhong wrote:
...snip...
>The QinQ didn't mean that the first(outer) tag must be 802.1ad, and the second(inner) tag must be 802.1q,
Do you have a quote for that from the standard? What I know and read
everywhere is that the standard specifies the outer s-tag to always be
0x88A8.
The other thing is that we don't live in an ideal world and there are a
lot of non-standard implementations out there, which might use 0x8100,
0x9100, 0x9200, 0x9300... for the outer s-tag, that's why using the
user-provided proto is better.
next prev parent reply other threads:[~2014-03-19 6:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 10:43 [PATCH net-next v2 0/3] bonding: support QinQ for bond arp interval Ding Tianhong
2014-03-18 10:43 ` [PATCH net-next v2 1/3] vlan: make a new function vlan_dev_vlan_proto() and export Ding Tianhong
2014-03-18 10:43 ` [PATCH net-next v2 2/3] bonding: support QinQ for bond arp interval Ding Tianhong
2014-03-18 12:05 ` Veaceslav Falico
2014-03-18 17:59 ` Jay Vosburgh
2014-03-18 19:27 ` Veaceslav Falico
2014-03-19 1:29 ` Ding Tianhong
2014-03-19 5:39 ` Veaceslav Falico [this message]
2014-03-19 11:16 ` Ding Tianhong
2014-03-18 10:43 ` [PATCH net-next v2 3/3] bonding: convert pr_xxx() to pr_xxx_ratelimited() for " Ding Tianhong
2014-03-18 11:01 ` Joe Perches
2014-03-18 11:14 ` Joe Perches
2014-03-18 11:28 ` Ding Tianhong
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=20140319053958.GA1242@redhat.com \
--to=vfalico@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--cc=fubar@us.ibm.com \
--cc=kaber@trash.net \
--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).