From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: cloud@xdp-project.net, brouer@redhat.com
Subject: [xdp-cloud] Re: seed code for xdp-cloud repo
Date: Tue, 9 Feb 2021 15:02:03 +0100 [thread overview]
Message-ID: <20210209150203.37a5a12f@carbon> (raw)
In-Reply-To: <3091252c-196b-d7c5-896e-567efbedbcf1@gmail.com>
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.
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
next prev parent reply other threads:[~2021-02-09 14: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 ` Jesper Dangaard Brouer [this message]
2021-02-09 16:02 ` [xdp-cloud] " David Ahern
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=20210209150203.37a5a12f@carbon \
--to=brouer@redhat.com \
--cc=cloud@xdp-project.net \
--cc=dsahern@gmail.com \
/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