From: Daniel Borkmann <dborkman@redhat.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "Eric Dumazet" <eric.dumazet@gmail.com>,
"Michal Sekletár" <sekletar.m@gmail.com>,
"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, 06 Dec 2013 13:04:50 +0100 [thread overview]
Message-ID: <52A1BD62.50605@redhat.com> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B7469@saturn3.aculab.com>
On 12/06/2013 12:15 PM, David Laight wrote:
>> From: Daniel Borkmann
>> Haven't had a closer look at the BSD BPF code /yet/, so ...
>
> I've not looked either.
>
>> i) Does BSD have such extensions and if so do we overlap some?
>>
>> ii) Is it planned to also introduce SO_BPF_EXTENSIONS for BSD kernels
>> to have one common api (that i.e. libpcap would then make use of)?
>
> If it is useful to add any of the extensions, and they don't collide
> with any other existing changes, then they might be added.
> Adding a request that indicates which extensions are supported should
> be easier than adding the extensions themselves.
Btw, we have aa1113d9f85da5 for that, but I see the point to get all
at once.
Ideally, they shouldn't even be added manually to this getsockopt,
plus we need to be careful of not preventing us in future from adding
additional extensions if they are needed for some good reason (hence,
the 1 bit, but maybe there's another better solution; haven't had
time to think about it so far).
next prev parent reply other threads:[~2013-12-06 12:05 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 [this message]
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=52A1BD62.50605@redhat.com \
--to=dborkman@redhat.com \
--cc=David.Laight@ACULAB.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).