From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mail.toke.dk (Postfix) with ESMTPS id 05D6A7E0813 for ; Tue, 9 Feb 2021 15:02:18 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=IcIZCh6A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1612879336; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3dBdJ3rPe4FLEHTndeX//ZIYiV7jZQG43hin7mf3b18=; b=IcIZCh6AZ71RxYTAZNhTs76uR9Zx0uan305ZuPabiJ397/QYVrQKgVFWOSBTLIQmndNXYr hn6YQ5qRqfN8TWm7uoq1/ZL9tQ4pY3zmWks2vcJMN/kw2AmeqyS4TJgfvuhif1Fru+Hy4I NI70OluEQQgKomDXQ0u10/gt2YFdhY8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-42-RCR59HUJNluSmkJdtYLgWg-1; Tue, 09 Feb 2021 09:02:13 -0500 X-MC-Unique: RCR59HUJNluSmkJdtYLgWg-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6F97B804036; Tue, 9 Feb 2021 14:02:12 +0000 (UTC) Received: from carbon (unknown [10.36.110.45]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8318A5D9C0; Tue, 9 Feb 2021 14:02:04 +0000 (UTC) Date: Tue, 9 Feb 2021 15:02:03 +0100 From: Jesper Dangaard Brouer To: David Ahern Message-ID: <20210209150203.37a5a12f@carbon> In-Reply-To: <3091252c-196b-d7c5-896e-567efbedbcf1@gmail.com> References: <3091252c-196b-d7c5-896e-567efbedbcf1@gmail.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=brouer@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID-Hash: 75QV5GQEUAXHIBKISVDX3FDIF45VJQ3O X-Message-ID-Hash: 75QV5GQEUAXHIBKISVDX3FDIF45VJQ3O X-MailFrom: brouer@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: cloud@xdp-project.net, brouer@redhat.com X-Mailman-Version: 3.3.2 Precedence: list Subject: [xdp-cloud] Re: seed code for xdp-cloud repo List-Id: XDP in the cloud Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 8 Feb 2021 20:37:14 -0700 David Ahern wrote: > I recall you had thoughts about initial seed code - something other than > just pulling what I have in my bpf-progs repo - e.g., the l2fwd code. > Anything I can do to help get this kickstarted? My concerns with your repo[1] is primarily how you integrate libbpf. E.g. I don't like having libbpf.a directly part of the repo. Toke and I have created a repo for bpf-examples[2], that we believe have a better integration (and auto-detection) for libbpf. I will prefer we can create a similar build environment in our xdp-cloud[3] git repo. The repo[3] already exist, but without any code. If you have time, you can look at bpf-examples[2] and see what you think, and maybe even go ahead and create the build env if you like our approach. Note, I do plan to make some changes[4] to bpf-examples around splitting the include files into two directories, to make it more clear what comes from kernel and what belong to project itself. [1] https://github.com/dsahern/bpf-progs/tree/master/libbpf/usr/lib64 [2] https://github.com/xdp-project/bpf-examples/ [3] https://github.com/xdp-project/xdp-cloud [4] https://github.com/xdp-project/bpf-examples/pull/8#issuecomment-760088297 -- Best regards, Jesper Dangaard Brouer MSc.CS, Principal Kernel Engineer at Red Hat LinkedIn: http://www.linkedin.com/in/brouer