From: Daniel Borkmann <dborkman@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jhs@mojatatu.com,
stephen@networkplumber.org, ast@plumgrid.com
Subject: Re: [patch net-next] tc: add BPF based action
Date: Wed, 07 Jan 2015 19:33:39 +0100 [thread overview]
Message-ID: <54AD7C03.3010904@redhat.com> (raw)
In-Reply-To: <1420649035-9522-1-git-send-email-jiri@resnulli.us>
On 01/07/2015 05:43 PM, Jiri Pirko wrote:
> This action provides a possibility to exec custom BPF code.
Can you elaborate a bit more on the particular use-case, and
what scenarios are unsolveable with the BPF filter we already
have in tc? Just wondering, since you're using BPF for the
purpose of classifying (but just from the context of actions)
what about a possibility of a generic container for reusing
(any) classifier from the framework, so we would not need to
duplicate code?
On the other hand, I would understand if it's at some point in
time eBPF which would f.e. mangle the packet, but the API you
propose is clearly classic BPF. ;)
Thanks,
Daniel
next prev parent reply other threads:[~2015-01-07 18:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 16:43 [patch net-next] tc: add BPF based action Jiri Pirko
2015-01-07 16:47 ` [patch iproute2 1/2] tc: push bpf common code into separate file Jiri Pirko
2015-01-07 16:47 ` [patch iproute2 2/2] tc: add support for BPF based actions Jiri Pirko
2015-01-07 18:50 ` Cong Wang
2015-01-07 19:52 ` Jiri Pirko
2015-01-07 19:58 ` Cong Wang
2015-01-14 1:19 ` Stephen Hemminger
2015-01-14 9:19 ` Jiri Pirko
2015-01-07 18:33 ` Daniel Borkmann [this message]
2015-01-07 18:46 ` [patch net-next] tc: add BPF based action Cong Wang
2015-01-08 7:26 ` Jiri Pirko
2015-01-08 14:55 ` Hannes Frederic Sowa
2015-01-08 15:01 ` Jiri Pirko
-- strict thread matches above, loose matches on Subject: below --
2015-01-08 19:04 Alexei Starovoitov
2015-01-12 10:52 ` Jiri Pirko
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=54AD7C03.3010904@redhat.com \
--to=dborkman@redhat.com \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).