From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>,
"David Marchand" <david.marchand@redhat.com>,
"Ray Kinsella" <mdr@ashroe.eu>,
"Jerin Jacob" <jerinj@marvell.com>,
"Sunil Kumar Kori" <skori@marvell.com>,
"Harry van Haaren" <harry.van.haaren@intel.com>, <dev@dpdk.org>
Cc: <techboard@dpdk.org>
Subject: The EAL is bloated
Date: Fri, 26 Aug 2022 10:58:15 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D872B5@smartserver.smartshare.dk> (raw)
Dear all,
<rant>
The "Environment Abstraction Layer" is expanding far beyond its purpose...
It not only includes abstractions for the underlying CPU Arch and O/S, but also a bunch of generic utility functions. In an ideal world, these belong in a Utility library; but I can live with them staying in the EAL library.
However, since the Utility features are also considered part of the EAL library, some features get misclassified as Utilities and thus sneak into the EAL library, regardless that they are completely independent of the underlying CPU Arch and O/S. E.g.: Service Cores, Trace, and soon the Lcore Poll Busyness library.
The EAL is not a catch-all library, and we should not allow the EAL to grow like this!
</rant>
If this misbehavior doesn't stop naturally, I propose that adding any new feature to the EAL requires techboard approval.
-Morten
next reply other threads:[~2022-08-26 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 8:58 Morten Brørup [this message]
2022-08-26 10:46 ` Bruce Richardson
2022-08-26 11:33 ` Morten Brørup
2022-08-26 12:36 ` Thomas Monjalon
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=98CBD80474FA8B44BF855DF32C47DC35D872B5@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=skori@marvell.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).