From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 67CA0C43334 for ; Fri, 10 Jun 2022 22:02:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233984AbiFJWCD (ORCPT ); Fri, 10 Jun 2022 18:02:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43122 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347622AbiFJWBr (ORCPT ); Fri, 10 Jun 2022 18:01:47 -0400 Received: from mail-vk1-xa2b.google.com (mail-vk1-xa2b.google.com [IPv6:2607:f8b0:4864:20::a2b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6FD6628991; Fri, 10 Jun 2022 15:01:41 -0700 (PDT) Received: by mail-vk1-xa2b.google.com with SMTP id b81so135267vkf.1; Fri, 10 Jun 2022 15:01:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=w2a8MMLStqGJpbQ4JSgaViyo56QdxV8uBLXeFRfLzZA=; b=otobDhQqCuLfav9uUR0LrUWEU/Vv3KserzOoodVW5JloOdft+NWYyD00xC8miK8//j HmZSu6kZABFqN6MXEhJPaMmfs+bd+xydaN/JHYlJCIY8npPigfQ2KZLLXcenSYTwVkUq I2a3L/3o8koe0w8G4Mz5rgxhMJlVekxoOQtX7vFkcmhyXw5cbVKlwUa8DQVDGiwkgS7F zumoO+oB44mWtrGgrziT24sqpb3OlVbwbWyL/Rqmy8fsyP5e8ESQorvaumG9uGnFNtus 84Yum2l5n9qrc5gyIlqqRVEjSaIKkCYHSfIegEFFitE2qbNRFDpG1uR9yQZLygLeEdzl /BhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=w2a8MMLStqGJpbQ4JSgaViyo56QdxV8uBLXeFRfLzZA=; b=P3MoD/+L4dlssZjgECw282S+lJnY3cy7qHLQedxuFZkbc4yKBB3ykPFq/Gx0KmM3sq ZFxLWxJdvnU1PAeSWEHCRFvlgEQncBXWNYhWrCreLStpWLElseX++b/9PgkQVuUnhGRl U3ZEYYxaaJouWjlHB8OXofUwMM+rHiIq2OwWZtv3ODzpBhZxkjT0NTizGha58xwPpz1F FvE89pyRqMbVXAzwZrtHQleP3LH/r2Y6ScA7JbG4ho9rnbxNARHWwiEGOisjbfVhxQX/ TnOtzWYVOoGf/vqkkKKeuNZ+B1ekipXMXrNI+3dzNhO2QcZQZdJ3tdPRHnKu+ATt44ce L5Bw== X-Gm-Message-State: AOAM530SD/Ad2CCHKnPQF/UfOEAm9riFxY+qwzM0Ba/Cxx9iY8LFH85L U7kzBy03+iOBXy45J9TlTNMQxfkn4Hw6CtkKQns= X-Google-Smtp-Source: ABdhPJxXS7fcyS0Zk2DkkIeJOAb7As0nkwoPY81uVrTfRSK9ZYOewpLGdt4u0//afvJme9m/O3YWa5SpnD6y7auFvoA= X-Received: by 2002:a1f:4c87:0:b0:365:4211:1121 with SMTP id z129-20020a1f4c87000000b0036542111121mr1997736vka.12.1654898500633; Fri, 10 Jun 2022 15:01:40 -0700 (PDT) MIME-Version: 1.0 References: <20210604063116.234316-1-memxor@gmail.com> <20220610125830.2tx6syagl2rphl35@apollo.legion> <20220610193418.4kqpu7crwfb5efzy@apollo.legion> In-Reply-To: From: Joanne Koong Date: Fri, 10 Jun 2022 15:01:29 -0700 Message-ID: Subject: Re: [PATCH bpf-next v2 0/7] Add bpf_link based TC-BPF API To: Daniel Borkmann Cc: Kumar Kartikeya Dwivedi , bpf , Alexei Starovoitov , Andrii Nakryiko , Jamal Hadi Salim , Vlad Buslov , Cong Wang , Jesper Dangaard Brouer , =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , netdev , John Fastabend Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On Fri, Jun 10, 2022 at 1:04 PM Daniel Borkmann wrote: > > Hi Joanne, hi Kumar, > > On 6/10/22 9:34 PM, Kumar Kartikeya Dwivedi wrote: > > On Sat, Jun 11, 2022 at 12:37:50AM IST, Joanne Koong wrote: > >> On Fri, Jun 10, 2022 at 10:23 AM Joanne Koong wrote: > >>> On Fri, Jun 10, 2022 at 5:58 AM Kumar Kartikeya Dwivedi > >>> wrote: > >>>> On Fri, Jun 10, 2022 at 05:54:27AM IST, Joanne Koong wrote: > >>>>> On Thu, Jun 3, 2021 at 11:31 PM Kumar Kartikeya Dwivedi > >>>>> wrote: > [...] > >>>> I can have a look at resurrecting it later this month, if you're ok with waiting > >>>> until then, otherwise if someone else wants to pick this up before that it's > >>>> fine by me, just let me know so we avoid duplicated effort. Note that the > >>>> approach in v2 is dead/unlikely to get accepted by the TC maintainers, so we'd > >>>> have to implement the way Daniel mentioned in [0]. > >>> > >>> Sounds great! We'll wait and check back in with you later this month. > >>> > >> After reading the linked thread (which I should have done before > >> submitting my previous reply :)), if I'm understanding it correctly, > >> it seems then that the work needed for tc bpf_link will be in a new > >> direction that's not based on the code in this v2 patchset. I'm > >> interested in learning more about bpf link and tc - I can pick this up > >> to work on. But if this was something you wanted to work on though, > >> please don't hesitate to let me know; I can find some other bpf link > >> thing to work on instead if that's the case. > > The tc ingress/egress overhaul we also discussed at lsf/mm/bpf in our session > with John and pretty much is along the lines as in the earlier link you sent. > We need it from Cilium & Tetragon as well, so it's wip from our side at the > moment, modulo the bpf link part. Would you be okay if I pinged you once something > that is plateable is ready? Yeah definitely! Thanks for letting me know! > > Thanks, > Daniel