public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Alexei Starovoitov <ast@plumgrid•com>
To: Daniel Borkmann <daniel@iogearbox•net>, davem@davemloft•net
Cc: netdev@vger•kernel.org, Thomas Graf <tgraf@suug•ch>
Subject: Re: [PATCH net-next 2/2] ebpf: add helper to retrieve net_cls's classid cookie
Date: Wed, 15 Jul 2015 14:06:22 -0700	[thread overview]
Message-ID: <55A6CB4E.1080307@plumgrid.com> (raw)
In-Reply-To: <9862a6b8778d344e8e10380060f09b161caac12f.1436961536.git.daniel@iogearbox.net>

On 7/15/15 5:21 AM, Daniel Borkmann wrote:
> It would be very useful to retrieve the net_cls's classid from an eBPF
> program to allow for a more fine-grained classification, it could be
> directly used or in conjunction with additional policies. I.e. docker,
> but also tooling such as cgexec, can easily run applications via net_cls
> cgroups:
>
>    cgcreate -g net_cls:/foo
>    echo 42 > foo/net_cls.classid
>    cgexec -g net_cls:foo <prog>
>
> Thus, their respecitve classid cookie of foo can then be looked up on
> the egress path to apply further policies. The helper is desigend such
> that a non-zero value returns the cgroup id.
>
> Signed-off-by: Daniel Borkmann<daniel@iogearbox•net>
> Cc: Thomas Graf<tgraf@suug•ch>

looks good to me.
Acked-by: Alexei Starovoitov <ast@plumgrid•com>

  reply	other threads:[~2015-07-15 21:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 12:21 [PATCH net-next 0/2] BPF update Daniel Borkmann
2015-07-15 12:21 ` [PATCH net-next 1/2] cls_cgroup: factor out classid retrieval Daniel Borkmann
2015-07-15 12:21 ` [PATCH net-next 2/2] ebpf: add helper to retrieve net_cls's classid cookie Daniel Borkmann
2015-07-15 21:06   ` Alexei Starovoitov [this message]
2015-07-20 19:41 ` [PATCH net-next 0/2] BPF update 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=55A6CB4E.1080307@plumgrid.com \
    --to=ast@plumgrid$(echo .)com \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=davem@davemloft$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=tgraf@suug$(echo .)ch \
    /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