From: Josef Bacik <josef@toxicpanda.com>
To: Joel Fernandes <joelaf@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
iovisor-dev@lists.iovisor.org,
Alexei Starovoitov <ast@kernel.org>,
Brendan Gregg <bgregg@netflix.com>,
bblanco@plumgrid.com, Alison Chaiken <alison@she-devel.com>,
"Cc: Android Kernel" <kernel-team@android.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Josef Bacik <jbacik@fb.com>, Yonghong Song <yhs@fb.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: ANNOUNCE: bpfd - a remote proxy daemon for executing bpf code (with corres. bcc changes)
Date: Thu, 25 Jan 2018 10:32:24 -0500 [thread overview]
Message-ID: <20180125153223.rd2vvkowrdtntkkl@destiny> (raw)
In-Reply-To: <CAJWu+ooMy4-DJtQMkGrCSVtJtnaWi4EdnK4_PK+n=FER1bFzvg@mail.gmail.com>
On Wed, Jan 24, 2018 at 08:29:39PM -0800, Joel Fernandes wrote:
> Hi Guys,
>
> Just providing an update: I made lots of progress last few weeks and
> all the issues mentioned below (in the last post) are resolved.
> I published an LWN article explaining the design of BPFd and BCC-side
> changes: https://lwn.net/SubscriberLink/744522/ba023b555957408e/
>
> There are still a few things that don't work well like symbol
> resolution, and I am working on it. The effect is just tools that need
> it wont work, which aren't that many from what I see but the goal is
> to get everything working ultimately.
>
> My next steps are to post the BCC side changes on github as a pull
> request (once I get a chance to rebase and send along with any clean
> ups). I also request you to take a look at the top 7 patches on this
> branch and provide any early feedback to me:
> https://github.com/joelagnel/bcc/commits/bcc-bpfd
>
> Based on activity on twitter and folks pinging me, it seems there is a
> LOT of interest for this both within Google and outside so its quite
> exciting. I strongly believe this will expand the use of BCC in the
> community. I look forward to presenting some demos at SCALE showing it
> in action.
>
> I am looking forward to your comments. Thanks.
I added a bunch of comments on github, I hope that's fine, otherwise I can dig
them out and post them in here. All in all everything looks good, I just have
some concerns about how the remote stuff is bolted into the python bindings.
Thanks for doing this, it's a great start,
Josef
prev parent reply other threads:[~2018-01-25 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 8:58 Joel Fernandes
2017-12-29 9:00 ` Joel Fernandes
2018-01-25 4:29 ` Joel Fernandes
2018-01-25 4:30 ` Joel Fernandes
2018-01-25 15:32 ` Josef Bacik [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=20180125153223.rd2vvkowrdtntkkl@destiny \
--to=josef@toxicpanda.com \
--cc=alison@she-devel.com \
--cc=ast@kernel.org \
--cc=bblanco@plumgrid.com \
--cc=bgregg@netflix.com \
--cc=iovisor-dev@lists.iovisor.org \
--cc=jbacik@fb.com \
--cc=joelaf@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=yhs@fb.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
all inboxes | Powered by JetHome®