From: Stephen Hemminger <stephen@networkplumber.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@plumgrid.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -next] f_bpf: allow for optional classid and add flags
Date: Mon, 12 Oct 2015 09:42:23 -0700 [thread overview]
Message-ID: <20151012094223.620c02ce@urahara> (raw)
In-Reply-To: <efad6a0f1fc08df554d5b0d0b36fb3dde4afe131.1443176477.git.daniel@iogearbox.net>
On Fri, 25 Sep 2015 12:32:41 +0200
Daniel Borkmann <daniel@iogearbox.net> wrote:
> When having optional classid, most minimal command can be sth
> like:
>
> tc filter add dev foo parent X: bpf obj prog.o
>
> Therefore, adapt the code so that a next argument will not be
> enforced as the case currently.
>
> Also, minor cleanup on the classid, where we should rather
> have used addattr32(), and add flags for exec configuration,
> for example (using short notation):
>
> tc filter add dev foo parent X: bpf da obj prog.o
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Applied to net-next branch of iproute2
prev parent reply other threads:[~2015-10-12 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 10:32 [PATCH iproute2 -next] f_bpf: allow for optional classid and add flags Daniel Borkmann
2015-09-25 14:58 ` Alexei Starovoitov
2015-10-12 16:42 ` Stephen Hemminger [this message]
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=20151012094223.620c02ce@urahara \
--to=stephen@networkplumber.org \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox