From: David Miller <davem@davemloft.net>
To: David.Laight@ACULAB.COM
Cc: eric.dumazet@gmail.com, sekletar.m@gmail.com,
dborkman@redhat.com, msekleta@redhat.com, netdev@vger.kernel.org,
mtk.manpages@gmail.com
Subject: Re: [PATCH] net: introduce SO_BPF_EXTENSIONS
Date: Fri, 06 Dec 2013 12:10:04 -0500 (EST) [thread overview]
Message-ID: <20131206.121004.406077340286411332.davem@davemloft.net> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B7466@saturn3.aculab.com>
From: "David Laight" <David.Laight@ACULAB.COM>
Date: Fri, 6 Dec 2013 09:50:49 -0000
>> if SO_BPF_EXTENSIONS is supported, than you can assume that all current
>> extensions are supported.
>>
>> No need to consume one bit per feature, as all these features wont ever
>> disappear from linux.
>
> However one of the BSDs could add a subset of the features and
> wish to advertise the fact.
> So using extra flags for non-trivial extensions could be useful.
Sorry, we're not going to accomodate this.
next prev parent reply other threads:[~2013-12-06 17:10 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
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 [this message]
-- 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=20131206.121004.406077340286411332.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@ACULAB.COM \
--cc=dborkman@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=msekleta@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sekletar.m@gmail.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).