XDP cloud mailing list archives
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: cloud@xdp-project.net
Subject: [xdp-cloud] Re: seed code for xdp-cloud repo
Date: Tue, 9 Feb 2021 09:02:09 -0700	[thread overview]
Message-ID: <20ca8603-5e75-729e-6861-32cf63b4031a@gmail.com> (raw)
In-Reply-To: <20210209150203.37a5a12f@carbon>

On 2/9/21 7:02 AM, Jesper Dangaard Brouer wrote:
> 
> On Mon, 8 Feb 2021 20:37:14 -0700 David Ahern <dsahern@gmail.com> 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.

Ease of use for a personal repo that moves across nodes, and I did not
want libbpf as a submodule. I also had changes to libbpf that just made
it easier to install a copy into the repo for rapid development.

> 
> 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.

ack.

      reply	other threads:[~2021-02-09 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  3:37 [xdp-cloud] " David Ahern
2021-02-09 14:02 ` [xdp-cloud] " Jesper Dangaard Brouer
2021-02-09 16:02   ` David Ahern [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

  List information: https://lists.xdp-project.net/postorius/lists/cloud.xdp-project.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20ca8603-5e75-729e-6861-32cf63b4031a@gmail.com \
    --to=dsahern@gmail.com \
    --cc=brouer@redhat.com \
    --cc=cloud@xdp-project.net \
    /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