From: Aaron Conole <aconole@redhat.com>
To: Adam Hassick <ahassick@iol.unh.edu>
Cc: ci@dpdk.org, alialnu@nvidia.com
Subject: Re: [PATCH v9 0/6] Community Lab Containers and Builder Engine
Date: Thu, 12 Oct 2023 09:01:22 -0400 [thread overview]
Message-ID: <f7t5y3catb1.fsf@redhat.com> (raw)
In-Reply-To: <20230811200018.5650-1-ahassick@iol.unh.edu> (Adam Hassick's message of "Fri, 11 Aug 2023 16:00:12 -0400")
Adam Hassick <ahassick@iol.unh.edu> writes:
> This patch series contains a new version of the DPDK CI containers. The old
> version was tied very tightly to the Community Lab Infrastructure, so it was
> not suitable for general use. This version is designed to make adding new
> OSes or OS versions as easy as possible. The minimum functionality can easily
> be built on any system that can compile DPDK. It includes support for
> building containers for other non-native architectures (ex: arm containers
> on x86) and for baking ABI references into the images.
>
> The inventory file as added in this patch series defines what the community lab
> currently supports.
>
> If you want to build these yourself, don't try to do parallel Makefile builds
> on non-server hardware. Libabigail is built into the containers, and since it
> is not avaliable in all distros it is compiled from source for many targets.
> If embedding the abi is enabled (DPDK_CI_CONTAINERS_BUILD_ABI=Y), with the
> current settings, DPDK will be compiled twice for every target in the
> inventory file. This will become three times when DPDK main has ABI stability
> again. Due to how the containers are constructed, building on non-native
> architectures is especially expensive because DPDK is compiled with an emulated
> compiler in a qemu vm that only has one thread.
> ---
Applied - thanks!
prev parent reply other threads:[~2023-10-12 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 20:00 Adam Hassick
2023-08-11 20:00 ` [PATCH v9 1/6] containers/docs: Add container builder start Adam Hassick
2023-08-11 20:00 ` [PATCH v9 2/6] containers/inventory: Add inventory for container builder Adam Hassick
2023-08-11 20:00 ` [PATCH v9 3/6] containers/builder: Dockerfile creation script Adam Hassick
2023-08-11 20:00 ` [PATCH v9 4/6] containers/templates: Templates for Dockerfiles Adam Hassick
2023-08-11 20:00 ` [PATCH v9 5/6] containers/container_builder: Container for python scripts Adam Hassick
2023-08-11 20:00 ` [PATCH v9 6/6] containers/Makefile: Makefile to automate builds Adam Hassick
2023-10-10 19:40 ` Aaron Conole
2023-10-10 20:08 ` Adam Hassick
2023-10-12 13:01 ` Aaron Conole [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7t5y3catb1.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).