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

Fix #1463, Implement separate allocator for task stacks #1464

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jphickey
Copy link
Contributor

Checklist (Please check before submitting)

Describe the contribution
Removes default use of malloc() for creating a task stack in VxWorks. Replace with a mempool-based solution, that can also be replaced with some other memory pool based on user preferences.

Fixes #1463

Testing performed
Coverage and sanity checking

Expected behavior changes
More user control over allocation of task stack, no malloc()

System(s) tested on
Debian

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

Removes default use of malloc() for creating a task stack in VxWorks.
Replace with a mempool-based solution, that can also be replaced with
some other memory pool based on user preferences.
@jphickey jphickey force-pushed the fix-1463-vxworks-task-mem branch from 6fea765 to 40eb028 Compare May 28, 2024 17:36
@jphickey jphickey added the CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) label Jun 20, 2024
@dzbaker
Copy link
Collaborator

dzbaker commented Jun 27, 2024

CCB 27 June 2024: Approved pending @jphickey running on sp0.

@dzbaker dzbaker added CCB:Provisionally-Approved and removed CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) labels Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Permit stack allocation from alternative memory pool on VxWorks
2 participants