From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751385AbeAYPc2 (ORCPT <rfc822;w@1wt.eu>);
        Thu, 25 Jan 2018 10:32:28 -0500
Received: from mail-qt0-f175.google.com ([209.85.216.175]:35328 "EHLO
        mail-qt0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751155AbeAYPc0 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 25 Jan 2018 10:32:26 -0500
X-Google-Smtp-Source: AH8x226ibZ8Jo0tsPHAsc1BSqrhdP7NDFOIIKKOty+skG0pyqX7vg+ZJMDnybE9Q/YmFr93iJcwb1g==
Date: Thu, 25 Jan 2018 10:32:24 -0500
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)
Message-ID: <20180125153223.rd2vvkowrdtntkkl@destiny>
References: <CAJWu+orZ9Hh-qy+ofdULQXobwBqDZSLEMhqZga7m2iWVuncsYQ@mail.gmail.com>
 <CAJWu+ooMy4-DJtQMkGrCSVtJtnaWi4EdnK4_PK+n=FER1bFzvg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJWu+ooMy4-DJtQMkGrCSVtJtnaWi4EdnK4_PK+n=FER1bFzvg@mail.gmail.com>
User-Agent: NeoMutt/20170714 (1.8.3)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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