From: Daniel Borkmann <daniel@iogearbox.net>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
stephen@networkplumber.org
Cc: ast@plumgrid.com, jiri@resnulli.us, tgraf@suug.ch,
netdev@vger.kernel.org, Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: [PATCH iproute2 -next] tc, bpf: finalize eBPF support for cls and act front-end
Date: Thu, 02 Apr 2015 02:24:13 +0200 [thread overview]
Message-ID: <551C8C2D.5060504@iogearbox.net> (raw)
In-Reply-To: <1427933636.1888890.248325033.0A76BE0D@webmail.messagingengine.com>
Hi Hannes,
On 04/02/2015 02:13 AM, Hannes Frederic Sowa wrote:
...
> Maybe a small utility programs like:
>
> bpf (--lookup|--update|--delete|--get-next-key) -fd
> filedescriptor-number (type conversion parameters here) key [value]
>
> So it can be easily used by shell scripts.
>
> For that the filedescriptor numbers would need to be exported (already
> opened) into a spawned shell and the numbers could be specified either
> in environment or just by printing text which can be sourced by shells
> (we already talked about the maybe exec 5</proc/pid/fd/1234 idea). Seems
> this can be just build ontop this current patch by extending the
> bpf-agent you already build, no?
I was thinking about that and trying it out, but as far as I can tell,
due to the anon inodes that are currently underlying as the fd provider,
it doesn't work w/o larger kernel changes. So, the file descriptor passing
is currently the only way to transfer control.
Cheers,
Daniel
next prev parent reply other threads:[~2015-04-02 0:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 22:35 [PATCH iproute2 -next] tc, bpf: finalize eBPF support for cls and act front-end Daniel Borkmann
2015-04-01 5:16 ` Alexei Starovoitov
2015-04-01 8:48 ` Daniel Borkmann
2015-04-01 12:36 ` Jamal Hadi Salim
2015-04-01 14:13 ` Daniel Borkmann
2015-04-01 22:30 ` Thomas Graf
2015-04-08 11:58 ` Jamal Hadi Salim
2015-04-02 0:13 ` Hannes Frederic Sowa
2015-04-02 0:24 ` Daniel Borkmann [this message]
2015-04-02 0:29 ` Hannes Frederic Sowa
2015-04-02 10:19 ` Daniel Borkmann
2015-04-02 11:30 ` Hannes Frederic Sowa
2015-04-02 12:08 ` Daniel Borkmann
2015-04-02 16:14 ` Alexei Starovoitov
2015-04-02 18:38 ` Daniel Borkmann
2015-04-02 12:10 ` Thomas Graf
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=551C8C2D.5060504@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@plumgrid.com \
--cc=hannes@stressinduktion.org \
--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 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).