Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce memory use with MISSION defines to size tlm vs PLATFORM defines for internal table use #1103

Open
skliper opened this issue Jan 19, 2021 · 0 comments

Comments

@skliper
Copy link
Contributor

skliper commented Jan 19, 2021

Is your feature request related to a problem? Please describe.
Spawned from #945 discussions where the point was brought up that PLATFORM defines could be used to size internal arrays for tracking (for example CFE_PLATFORM_ES_PERF_MAX_IDS and CFE_PLATFORM_ES_MAX_APPLICATIONS) and MISSION defines could be used for sizing tlm (so all platforms have the same packet definitions).

Describe the solution you'd like
Trade the additional requirements/complexity vs memory savings. Consider requirements/design/implementation updates. If required, identify prime stakeholder and resources to implement.

Describe alternatives you've considered
Leave as is where the mission maximums are used for both tlm and internal sizing (current state meets current requirements).

Additional context
#945

Requester Info
Jacob Hageman - NASA/GSFC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant