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
