From: Daniel Borkmann <daniel@iogearbox•net>
To: Jamal Hadi Salim <jhs@mojatatu•com>,
Alexei Starovoitov <ast@plumgrid•com>,
"David S. Miller" <davem@davemloft•net>
Cc: John Fastabend <john.fastabend@gmail•com>, netdev@vger•kernel.org
Subject: Re: [PATCH v2 net-next 1/2] cls_bpf: introduce integrated actions
Date: Fri, 18 Sep 2015 14:51:34 +0200 [thread overview]
Message-ID: <55FC08D6.9050405@iogearbox.net> (raw)
In-Reply-To: <55FBFFF8.3050101@mojatatu.com>
Hi Jamal,
On 09/18/2015 02:13 PM, Jamal Hadi Salim wrote:
...
> The architecture is about small tools that come together to
> provide complex processing. ebpf may be the best classifier
> today - but by no means the only one or guaranteed that nothing
> better will exist for speficic use cases.
Yes, I agree, I think nobody claimed that, and it also doesn't
limit anyone from their choices of configuration possibilities
one can do nowadays.
> If there is something in the core that needs improvement
> for the benefit of all, then lets do that.
Yeah, I think i.e. since the last couple of months that is already
happening from various people.
Thanks,
Daniel
next prev parent reply other threads:[~2015-09-18 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 6:05 [PATCH v2 net-next 0/2] bpf: performance improvements Alexei Starovoitov
2015-09-16 6:05 ` [PATCH v2 net-next 1/2] cls_bpf: introduce integrated actions Alexei Starovoitov
2015-09-17 12:37 ` Jamal Hadi Salim
2015-09-17 13:13 ` Daniel Borkmann
2015-09-17 15:19 ` Alexei Starovoitov
2015-09-18 12:13 ` Jamal Hadi Salim
2015-09-18 12:51 ` Daniel Borkmann [this message]
2015-09-18 12:04 ` Jamal Hadi Salim
2015-09-16 6:05 ` [PATCH v2 net-next 2/2] bpf: add bpf_redirect() helper Alexei Starovoitov
2015-09-16 6:45 ` John Fastabend
2015-09-18 4:10 ` [PATCH v2 net-next 0/2] bpf: performance improvements 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=55FC08D6.9050405@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=ast@plumgrid$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jhs@mojatatu$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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