netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas F Herbert <thomasfherbert@gmail.com>
To: Pravin Shelar <pshelar@nicira.com>
Cc: netdev <netdev@vger.kernel.org>,
	ccp@atcnet.net, "dev@openvswitch.org" <dev@openvswitch.org>,
	therbert@redhat.com
Subject: Re: [ovs-dev] [PATCH net-next V8 2/2] openvswitch: 802.1ad: Flow handling, actions, and parsing
Date: Tue, 12 May 2015 20:04:46 -0400	[thread overview]
Message-ID: <5552951E.4080605@gmail.com> (raw)
In-Reply-To: <CALnjE+rQBn3DB0p+NP_hkXDkoTWCB_HKhjo8wM0-VvOSLzO46w@mail.gmail.com>

On 5/6/15 2:36 PM, Pravin Shelar wrote:
> On Tue, May 5, 2015 at 8:51 AM, Thomas F Herbert
> <thomasfherbert@gmail.com> wrote:
>> Add support for 802.1ad including the ability to push and pop double
>> tagged vlans.
>>
>> Signed-off-by: Thomas F Herbert <thomasfherbert@gmail.com>
>> ---
 >....
> checkpatch.pl complains about blank lines.
Pravin, Thanks for your review.
Fixed in V9
>
>>
>>....
> I think we need to invalidate the flow key even when protocol is
> 8021Q. This is because packet is changed from double vlan
> encapsulation to single. In this case vlan 8021Q TCI is mapped to
> different key struct member.
Yes, good catch and thanks. this extra check in the pop and push actions 
wasn't necessary. The original push and pop code in net-next was already 
qinq-ready.
>
>>....
> Same goes here, we need to invalidate flow key here.
See above.
>
>>          else
>>                  key->eth.tci = vlan->vlan_tci;
>> diff --git a/net/openvswitch/flow.c b/net/openvswitch/flow.c
>> index 2dacc7b..0430466 100644
>> --- a/net/openvswitch/flow.c
>> +++ b/net/openvswitch/flow.c
>> @@ -298,21 +298,79 @@ static bool icmp6hdr_ok(struct sk_buff *skb)
>>   static int parse_vlan(struct sk_buff *skb, struct sw_flow_key *key)
>>...
>> +                       if (unlikely(skb->len < sizeof(struct qtag_prefix) +
>> +                                       sizeof(__be16)))
>> +                               return 0;
>> +
> In case of error we need to clear key->eth.tci.
Done. Fixed in V9
>
>
> Move local variable declaration to block where it is actually used.
Done. Fixed in V9
>

> Can you move this vlan key parsing to separate function.
Good idea. In V9, Vlan to key parsing is now consolidated in a separate 
function.
>
>

> I do not see key->eth.ctci mask set according to userspace mask attribute.
> You could use ovs_nested_vlan_from_nlattrs().
Fixed in V9.
>


-- 
Thomas F. Herbert

      reply	other threads:[~2015-05-13  0:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 15:51 [PATCH net-next V8 0/2] openvswitch: Add support for 802.1AD Thomas F Herbert
     [not found] ` <1430841087-20764-1-git-send-email-thomasfherbert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-05 15:51   ` [PATCH net-next V8 1/2] openvswitch: 802.1ad uapi changes Thomas F Herbert
2015-05-05 15:51   ` [PATCH net-next V8 2/2] openvswitch: 802.1ad: Flow handling, actions, and parsing Thomas F Herbert
2015-05-06 18:36     ` [ovs-dev] " Pravin Shelar
2015-05-13  0:04       ` Thomas F Herbert [this message]

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=5552951E.4080605@gmail.com \
    --to=thomasfherbert@gmail.com \
    --cc=ccp@atcnet.net \
    --cc=dev@openvswitch.org \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    --cc=therbert@redhat.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).