netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
To: Alexei Starovoitov <ast@plumgrid.com>,
	Michal Sekletar <msekleta@redhat.com>,
	netdev@vger.kernel.org
Cc: Jiri Pirko <jpirko@redhat.com>
Subject: Re: [PATCH] filter: introduce SKF_AD_VLAN_PROTO BPF extension
Date: Thu, 05 Mar 2015 11:28:19 +0900	[thread overview]
Message-ID: <54F7BF43.80203@lab.ntt.co.jp> (raw)
In-Reply-To: <54F77336.7040006@plumgrid.com>

On 2015/03/05 6:03, Alexei Starovoitov wrote:
> On 3/4/15 12:41 PM, Michal Sekletar wrote:
>> This commit introduces new BPF extension. It makes possible to load
>> value of
>> skb->vlan_proto (vlan tpid) to register A.
>>
>> Currently, vlan header is removed from frame and information is
>> available to
>> userspace only via tpacket interface. Hence, it is not possible to
>> install
>> filter which uses value of vlan tpid field.
>>
>> AFAICT only way how to filter based on tpid value is to reconstruct
>> original
>> frame encapsulation and interpret BPF filter code in userspace. Doing
>> that is
>> way slower than doing filtering in kernel.
>>
>> Cc: Alexei Starovoitov <ast@plumgrid.com>
>> Cc: Jiri Pirko <jpirko@redhat.com>
>> Signed-off-by: Michal Sekletar <msekleta@redhat.com>
>> ---
>> @@ -282,6 +282,7 @@ Possible BPF extensions are shown in the following
>> table:
>>     vlan_tci                              skb_vlan_tag_get(skb)
>>     vlan_pr                               skb_vlan_tag_present(skb)
>>     rand                                  prandom_u32()
>> +  vlan_proto                            skb->vlan_proto
> 
> the patch is correct and looks clean, but I don't understand
> the motivation for the patch.
> There is already SKF_AD_VLAN_TAG_PRESENT. If it is set then only
> two possible values of vlan_proto are ETH_P_8021Q or ETH_P_8021AD.
> If there another vlan header inside the packet, it's AD.

802.1ad can be used without an inner vlan tag.
Also, we can send/receive QinQ frames with 802.1Q outer tags.
(We can create vlan interface on 802.1Q vlan interface.)

Thanks,
Toshiaki Makita

  parent reply	other threads:[~2015-03-05  2:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 20:41 [PATCH] filter: introduce SKF_AD_VLAN_PROTO BPF extension Michal Sekletar
2015-03-04 21:03 ` Alexei Starovoitov
2015-03-04 21:14   ` Guy Harris
2015-03-04 23:47     ` Alexei Starovoitov
2015-03-05  6:50       ` Jiri Pirko
2015-03-05  7:23         ` Alexei Starovoitov
2015-03-05  7:24         ` Michal Kubecek
2015-03-05  7:49           ` Alexei Starovoitov
2015-03-05  8:35           ` Guy Harris
2015-03-05  9:23             ` Michal Kubecek
2015-03-05  2:28   ` Toshiaki Makita [this message]
2015-03-05  2:41     ` Alexei Starovoitov
2015-03-05 10:37   ` Michal Sekletar
2015-03-05 16:52     ` Alexei Starovoitov
2015-03-05 20:03       ` Daniel Borkmann
2015-03-05 20:40         ` Alexei Starovoitov
2015-03-06  8:09           ` Michal Sekletar
2015-03-06  9:04         ` Michal Sekletar
2015-03-06 17:23           ` Daniel Borkmann
2015-03-06 14:02         ` Michal Kubecek
2015-03-06 17:54           ` Daniel Borkmann
2015-03-05  8:52 ` Jiri Pirko
2015-03-05  8:57 ` Denis Kirjanov
2015-03-05 14:33   ` Michal Sekletar
2015-03-05 18:12   ` David Miller

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=54F7BF43.80203@lab.ntt.co.jp \
    --to=makita.toshiaki@lab.ntt.co.jp \
    --cc=ast@plumgrid.com \
    --cc=jpirko@redhat.com \
    --cc=msekleta@redhat.com \
    --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).