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 X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AB9CEC3524D for ; Tue, 4 Feb 2020 03:41:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8169C2080D for ; Tue, 4 Feb 2020 03:41:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="mJKKo1RQ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727156AbgBDDlp (ORCPT ); Mon, 3 Feb 2020 22:41:45 -0500 Received: from mail-qk1-f195.google.com ([209.85.222.195]:36333 "EHLO mail-qk1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726694AbgBDDlp (ORCPT ); Mon, 3 Feb 2020 22:41:45 -0500 Received: by mail-qk1-f195.google.com with SMTP id w25so16617816qki.3; Mon, 03 Feb 2020 19:41:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zzYHmVOeeAxyamF8Kpa4bj+CdDiTycRp7RrsQdQg0AY=; b=mJKKo1RQtv+WDSf/3pSDCmDci33yAJiV06eQYYLIdu4e7ZcLhNPFHFgxFd3T0I3pEQ dmBxStjANxkZJ816lIX6vWaxH+Tdek1eU9ozIp7BhQApEAgCxLSZoGB4mk4GEFzrACAL vzmudr5PdRWb6Q3NHqA+X2H/NY5ba5PQ0kAwiHSMnjojk8iSiEv1Wid+VhhH3BHXPgp/ BSZsis6TG9eVY2BGyrHOsMq3mtsLk1sXeoc9FnUzPPYXoKIaQ/3jTKa2HHhmO1gAmfga VJh67RF+tQ4GYxsWY6yjDasSSh/wD9ByJxPpj6BZLWAcMjh+QzWGkjeTCp/Ix2zc0dF3 oSqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zzYHmVOeeAxyamF8Kpa4bj+CdDiTycRp7RrsQdQg0AY=; b=jzdz3WqkmW9Bx2L1Q1gnPRLiQcKH7InLKU8KT2QvhEyysxQ1uec9FJBtpzdmUpkdAx ojcIoEx5h6RZFXnn3i+2nMazIuyTv1Xl/lfsoxMSe9PtN47/nUBTtgWYSBkvvVkPA5Uh a/eT+Cg3F7gqOlJQyAUZq7JOqVj1UOWEtIOiALlaIKHVaEfGXHLQ7/k9JvLz5uW9/hwc ylh+swYcvyQ2KPmDkhw1F41dD4gHanGGqnPVvN/fobscMRRyyKs0VNGtPyp0alwuVLyU 3hPAhIkSc5ySme9PMbc8/HhLF13531VCbynHJV41vqKi47rbzqiHkLPYiLIDHx7VGd2h 90oQ== X-Gm-Message-State: APjAAAXmgEuBoqnMzfhy0SZJUf/Ny+7EiweIWN7ScAle5HWMBLHRsJY9 JoVVJMxoKda/g6LsrcU6tAsQaCruWrZVpDx18Y4= X-Google-Smtp-Source: APXvYqzWq7Dxw5rd0EK8LUD75fgPlTfxQC1yBmBMWvRyA0+QvNRl9jkSbvqY2Op7lY0KrXJWYjMFin7LK0qwU9XMwJA= X-Received: by 2002:a05:620a:a54:: with SMTP id j20mr26563989qka.92.1580787704060; Mon, 03 Feb 2020 19:41:44 -0800 (PST) MIME-Version: 1.0 References: <20190820114706.18546-1-toke@redhat.com> <87blwiqlc8.fsf@toke.dk> <43e8c177-cc9c-ca0b-1622-e30a7a1281b7@iogearbox.net> <87tva8m85t.fsf@toke.dk> <87blqfcvnf.fsf@toke.dk> <0bf50b22-a8e2-e3b3-aa53-7bd5dd5d4399@gmail.com> In-Reply-To: <0bf50b22-a8e2-e3b3-aa53-7bd5dd5d4399@gmail.com> From: Andrii Nakryiko Date: Mon, 3 Feb 2020 19:41:33 -0800 Message-ID: Subject: Re: [RFC bpf-next 0/5] Convert iproute2 to use libbpf (WIP) To: David Ahern Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , Daniel Borkmann , Stephen Hemminger , Alexei Starovoitov , Martin KaFai Lau , Song Liu , Yonghong Song , David Miller , Jesper Dangaard Brouer , Networking , bpf Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Feb 3, 2020 at 5:46 PM David Ahern wrote: > > On 2/3/20 5:56 PM, Andrii Nakryiko wrote: > > Great! Just to disambiguate and make sure we are in agreement, my hope > > here is that iproute2 can completely delegate to libbpf all the ELF > > > > iproute2 needs to compile and continue working as is when libbpf is not > available. e.g., add check in configure to define HAVE_LIBBPF and move > the existing code and move under else branch. Wouldn't it be better to statically compile against libbpf in this case and get rid a lot of BPF-related code and simplify the rest of it? This can be easily done by using libbpf through submodule, the same way as BCC and pahole do it.