From: Daniel Borkmann <dborkman@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Michal Sekletar <msekleta@redhat.com>,
netdev@vger.kernel.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] net: introduce SO_BPF_EXTENSIONS
Date: Fri, 29 Nov 2013 15:13:03 +0100 [thread overview]
Message-ID: <5298A0EF.70401@redhat.com> (raw)
In-Reply-To: <1385659889.5352.25.camel@edumazet-glaptop2.roam.corp.google.com>
On 11/28/2013 06:31 PM, Eric Dumazet wrote:
> On Thu, 2013-11-28 at 12:57 +0100, Michal Sekletar wrote:
>
>> +enum {
>> + BPF_ANC_FLAG_PROTOCOL = (1 << 0),
>> + BPF_ANC_FLAG_PKTTYPE = (1 << 1),
>> + BPF_ANC_FLAG_IFINDEX = (1 << 2),
>> + BPF_ANC_FLAG_NLATTR = (1 << 3),
>> + BPF_ANC_FLAG_NLATTR_NEST = (1 << 4),
>> + BPF_ANC_FLAG_MARK = (1 << 5),
>> + BPF_ANC_FLAG_QUEUE = (1 << 6),
>> + BPF_ANC_FLAG_HATYPE = (1 << 7),
>> + BPF_ANC_FLAG_RXHASH = (1 << 8),
>> + BPF_ANC_FLAG_CPU = (1 << 9),
>> + BPF_ANC_FLAG_ALU_XOR_X = (1 << 10),
>> + BPF_ANC_FLAG_SECCOMP_LD_W = (1 << 11),
>> + BPF_ANC_FLAG_VLAN_TAG = (1 << 12),
>> + BPF_ANC_FLAG_VLAN_TAG_PRESENT = (1 << 13),
>> + BPF_ANC_FLAG_PAY_OFFSET = (1 << 14),
>> +};
>> +
>
> Why spending 15 bits (out of 32), for all these extensions ?
>
> It seems a single one should be enough.
>
> I do not think we will ever remove one of these extension.
Agreed, this will just cripple of us adding other extensions in
terms of uapi. I assume there won't be so much more extensions,
but it's of course hard to predict the future. ;-)
next prev parent reply other threads:[~2013-11-29 14:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 11:57 [PATCH] net: introduce SO_BPF_EXTENSIONS Michal Sekletar
2013-11-28 17:31 ` Eric Dumazet
2013-11-29 14:13 ` Daniel Borkmann [this message]
2013-12-05 17:28 ` Michal Sekletár
2013-12-05 17:32 ` Eric Dumazet
2013-12-06 9:50 ` David Laight
2013-12-06 10:02 ` Daniel Borkmann
2013-12-06 11:15 ` David Laight
2013-12-06 12:04 ` Daniel Borkmann
2013-12-06 17:15 ` David Miller
2013-12-09 14:09 ` Michal Sekletár
2013-12-10 0:25 ` David Miller
2013-12-06 17:10 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 16:14 Michal Sekletar
2014-01-16 16:41 ` Daniel Borkmann
2014-01-16 17:13 ` Michal Sekletar
2014-01-16 17:26 ` Michal Sekletar
2014-01-16 18:34 ` Daniel Borkmann
2014-01-16 18:49 ` Eric Dumazet
2014-01-16 18:52 ` Daniel Borkmann
2014-01-16 19:09 ` Eric Dumazet
2014-01-16 19:24 ` Daniel Borkmann
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=5298A0EF.70401@redhat.com \
--to=dborkman@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=msekleta@redhat.com \
--cc=mtk.manpages@gmail.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).