public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <ast@plumgrid.com>
To: He Kuang <hekuang@huawei.com>
Cc: wangnan0@huawei.com, LKML <linux-kernel@vger.kernel.org>,
	"daniel@iogearbox.net >> Daniel Borkmann" <daniel@iogearbox.net>
Subject: Re: [RFC] bpf: Suggestion on bpf syscall interface
Date: Mon, 30 Mar 2015 20:23:24 -0700	[thread overview]
Message-ID: <551A132C.9040805@plumgrid.com> (raw)
In-Reply-To: <5518BF6F.4080406@huawei.com>

On 3/29/15 8:13 PM, He Kuang wrote:
>
> By using current bpf syscalls, we should keep the program which
> attaches bpf programs running background, use it or some other
> processes communicate with it to adjust maps parameters, like
> sample rate for sys_write.

You can do all of the above by passing fds between processes. I still
don't see a need for sysfs.

> In current implementation, we have to use a large and relative
> heavy daemon to deal with loading, configuration, adjusting and
> unloading works together.

This daemon is actually small and simple.
Just take a look how Daniel did for tc:
http://patchwork.ozlabs.org/patch/456387/
In that example 3 programs are sharing maps and single bpf_agent
monitors maps. Note that tc loaded programs and exited while
agent keeps running. Very straightforward.


      reply	other threads:[~2015-03-31  3:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 11:36 [RFC] bpf: Suggestion on bpf syscall interface He Kuang
2015-03-28 17:21 ` Alexei Starovoitov
2015-03-28 22:16   ` Daniel Borkmann
2015-03-30  3:13   ` He Kuang
2015-03-31  3:23     ` Alexei Starovoitov [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=551A132C.9040805@plumgrid.com \
    --to=ast@plumgrid.com \
    --cc=daniel@iogearbox.net \
    --cc=hekuang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangnan0@huawei.com \
    /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