From: Alexei Starovoitov <ast@plumgrid.com>
To: Daniel Borkmann <daniel@iogearbox.net>, davem@davemloft.net
Cc: jhs@mojatatu.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] cls_bpf: further limit exec opcodes subset
Date: Wed, 23 Sep 2015 13:54:28 -0700 [thread overview]
Message-ID: <56031184.3030308@plumgrid.com> (raw)
In-Reply-To: <30adbc348f5fcefddff51c8155086a87b389ccdb.1443037354.git.daniel@iogearbox.net>
On 9/23/15 12:56 PM, Daniel Borkmann wrote:
> Jamal suggested to further limit the currently allowed subset of opcodes
> that may be used by a direct action return code as the intention is not
> to replace the full action engine, but rather to have a minimal set that
> can be used in the fast-path on things like ingress for some features
> that cls_bpf supports.
>
> Classifiers can, of course, still be chained together that have direct
> action mode with those that have a full exec pass. For more complex
> scenarios that go beyond this minimal set here, the full tcf_exts_exec()
> path must be used.
>
> Suggested-by: Jamal Hadi Salim<jhs@mojatatu.com>
> Signed-off-by: Daniel Borkmann<daniel@iogearbox.net>
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
next prev parent reply other threads:[~2015-09-23 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 19:56 [PATCH net-next 0/3] Minor cls_bpf updates Daniel Borkmann
2015-09-23 19:56 ` [PATCH net-next 1/3] cls_bpf: also dump TCA_BPF_FLAGS Daniel Borkmann
2015-09-23 20:52 ` Alexei Starovoitov
2015-09-23 19:56 ` [PATCH net-next 2/3] cls_bpf: make binding to classid optional Daniel Borkmann
2015-09-23 20:53 ` Alexei Starovoitov
2015-09-23 19:56 ` [PATCH net-next 3/3] cls_bpf: further limit exec opcodes subset Daniel Borkmann
2015-09-23 20:54 ` Alexei Starovoitov [this message]
2015-09-23 21:29 ` [PATCH net-next 0/3] Minor cls_bpf updates 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=56031184.3030308@plumgrid.com \
--to=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.