From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Jan Viktorin <viktorin@rehivetech.com>,
Ruifeng Wang <ruifeng.wang@arm.com>, dev <dev@dpdk.org>
Cc: Luca Boccassi <bluca@debian.org>
Subject: [dpdk-dev] Probing the expected state/support of DPDK@armhf
Date: Mon, 8 Nov 2021 13:32:10 +0100 [thread overview]
Message-ID: <CAATJJ0+6h5tcx9OYLAJ3+m_vvAAv+uuJ_BSyPuR4Vzu2SSR71g@mail.gmail.com> (raw)
Hi,
I wanted to ask about the current state of DPDK@armhf (not arm64, that
seems fine AFAICS).
Since there are too many arms today, I mean armhf as in [0].
What I see when building DPDK 21.11 is
2973 ../config/meson.build:364:1: ERROR: Problem encountered: Number
of CPU cores not specified.
Right now this seems to be broken the same everywhere - Suse [1],
fedora [2], Debian/Ubuntu [3]
I'm not asking for a fix for this particular issue (although I guess
people would be happy), but more about the general state of
DPDK@armhf.
Debian and Ubuntu used to build it on armhf as well, but over the
recent years I feel (no hard data) that usage there was next to none.
OTOH Thomas said that recently people cared about armv7 [4]
My suggestion would be to disable the build on armhf in Debian/Ubuntu
(+elsewhere?) until it reaches a more stable phase and real use-cases.
But maybe I missed some use-cases, therefore I wanted to reach out to
the mailing list to probe for more opinions on this.
Thanks for your thoughts on this in advance!
P.S. If it is meant to work and be supported, then we will need a fix for that
[0]: https://wiki.debian.org/ArmHardFloatPort
[1]: https://build.opensuse.org/public/build/home:bluca:dpdk/openSUSE_Factory_ARM/armv7l/dpdk/_log
[2]: https://build.opensuse.org/public/build/home:bluca:dpdk/Fedora_35/armv7l/dpdk/_log
[3]: https://launchpadlibrarian.net/567810935/buildlog_ubuntu-jammy-armhf.dpdk_21.11~rc1-1u~ppa1_BUILDING.txt.gz
[4]: https://patches.dpdk.org/project/dpdk/patch/20210610111839.7481-1-s.chandrakant@globaledgesoft.com/
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
next reply other threads:[~2021-11-08 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 12:32 Christian Ehrhardt [this message]
2021-11-09 7:17 ` Ruifeng Wang
2021-11-10 7:47 ` Christian Ehrhardt
2021-11-16 12:06 ` Juraj Linkeš
2021-11-17 6:44 ` Ruifeng Wang
2021-11-18 10:28 ` Juraj Linkeš
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=CAATJJ0+6h5tcx9OYLAJ3+m_vvAAv+uuJ_BSyPuR4Vzu2SSR71g@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ruifeng.wang@arm.com \
--cc=viktorin@rehivetech.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;
as well as URLs for NNTP newsgroup(s).