On Wed, 11 May 2016 12:06:35 +0900, Simon Horman wrote:
> Is this close to what you had in mind?

Yes but see below.

> @@ -739,17 +729,17 @@ int ovs_flow_key_extract(const struct ip_tunnel_info 
> *tun_info,
>       key->phy.skb_mark = skb->mark;
>       ovs_ct_fill_key(skb, key);
>       key->ovs_flow_hash = 0;
> -     key->phy.is_layer3 = is_layer3;
> +     key->phy.is_layer3 = (tun_info && skb->mac_len == 0);

Do we have to depend on tun_info? It would be nice to support all
ARPHRD_NONE interfaces, not just tunnels. The tun interface (from
the tuntap driver) comes to mind, for example.

> --- a/net/openvswitch/vport-netdev.c
> +++ b/net/openvswitch/vport-netdev.c
> @@ -60,7 +60,21 @@ static void netdev_port_receive(struct sk_buff *skb)
>       if (vport->dev->type == ARPHRD_ETHER) {
>               skb_push(skb, ETH_HLEN);
>               skb_postpush_rcsum(skb, skb->data, ETH_HLEN);
> +     } else if (vport->dev->type == ARPHRD_NONE) {
> +             if (skb->protocol == htons(ETH_P_TEB)) {
> +                     struct ethhdr *eth = eth_hdr(skb);
> +
> +                     if (unlikely(skb->len < ETH_HLEN))
> +                             goto error;
> +
> +                     skb->mac_len = ETH_HLEN;
> +                     if (eth->h_proto == htons(ETH_P_8021Q))
> +                             skb->mac_len += VLAN_HLEN;
> +             } else {
> +                     skb->mac_len = 0;
> +             }

Without putting much thought into this, could this perhaps be left for
parse_ethertype (called from key_extract) to do?

Thanks,

 Jiri

Reply via email to