All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <ast@plumgrid.com>
To: Daniel Borkmann <daniel@iogearbox.net>, stephen@networkplumber.org
Cc: jiri@resnulli.us, jhs@mojatatu.com, tgraf@suug.ch,
	netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -next v2] tc, bpf: finalize eBPF support for cls and act front-end
Date: Wed, 01 Apr 2015 09:02:38 -0700	[thread overview]
Message-ID: <551C169E.1080105@plumgrid.com> (raw)
In-Reply-To: <e253218a3cd6e0885a3884ec6dbbaabafd1bfe43.1427903335.git.daniel@iogearbox.net>

On 4/1/15 8:57 AM, Daniel Borkmann wrote:
> This work finalizes both eBPF front-ends for the classifier and action
> part in tc, it allows for custom ELF section selection, a simplified tc
> command frontend (while keeping compat), reusing of common maps between
> classifier and actions residing in the same object file, and exporting
> of all map fds to an eBPF agent for handing off further control in user
> space.
>
> It also adds an extensive example of how eBPF can be used, and a minimal
> self-contained example agent that dumps map data. The example is well
> documented and hopefully provides a good starting point into programming
> cls_bpf and act_bpf.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>

great work!
Acked-by: Alexei Starovoitov <ast@plumgrid.com>

  reply	other threads:[~2015-04-01 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 15:57 [PATCH iproute2 -next v2] tc, bpf: finalize eBPF support for cls and act front-end Daniel Borkmann
2015-04-01 16:02 ` Alexei Starovoitov [this message]
2015-04-01 22:15 ` Thomas Graf
2015-04-02  6:22 ` Jiri Pirko
2015-04-08 11:59   ` Jamal Hadi Salim
2015-04-08 12:33     ` Daniel Borkmann
2015-04-10 20:35 ` Stephen Hemminger

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=551C169E.1080105@plumgrid.com \
    --to=ast@plumgrid.com \
    --cc=daniel@iogearbox.net \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=tgraf@suug.ch \
    /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.