From: Veaceslav Falico <vfalico@redhat.com>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: 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: Tue, 18 Mar 2014 13:05:58 +0100 [thread overview]
Message-ID: <20140318120558.GA6430@redhat.com> (raw)
In-Reply-To: <1395139433-19576-3-git-send-email-dingtianhong@huawei.com>
On Tue, Mar 18, 2014 at 06:43:52PM +0800, Ding Tianhong wrote:
...snip...
>- if (vlan_id) {
>- skb = vlan_put_tag(skb, htons(ETH_P_8021Q), vlan_id);
>+ if (outer->vlan_id) {
>+ if (inner->vlan_id) {
>+ pr_debug("inner tag: proto %X vid %X\n",
>+ ntohs(inner->vlan_proto), inner->vlan_id);
>+ skb = __vlan_put_tag(skb, inner->vlan_proto, inner->vlan_id);
>+ if (!skb) {
>+ pr_err("failed to insert inner VLAN tag\n");
>+ return;
>+ }
>+ }
>+
>+ pr_debug("outer reg: proto %X vid %X\n",
>+ ntohs(outer->vlan_proto), outer->vlan_id);
>+ skb = vlan_put_tag(skb, outer->vlan_proto, outer->vlan_id);
If I read correctly then the inner->vlan_proto will always be ETH_P_8021AD,
whilst the outer will also always be ETH_P_8021Q. So I think it'd be a lot
easier (and more readable) to just pass 2 vlan ids, and set those protos
statically - that will save you from adding that new function to vlan core,
fro madding a new struct that you've added here and make it several lines
less.
next prev parent reply other threads:[~2014-03-18 12:06 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 [this message]
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
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=20140318120558.GA6430@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).