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.

Sign up for GitHub

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

Jump to bottom

Permit stack allocation from alternative memory pool on VxWorks #1463

Open
jphickey opened this issue May 24, 2024 · 0 comments · May be fixed by #1464
Open

Permit stack allocation from alternative memory pool on VxWorks #1463

jphickey opened this issue May 24, 2024 · 0 comments · May be fixed by #1464
Assignees
@jphickey
Labels
enhancement

Comments

@jphickey
Copy link
Contributor

Is your feature request related to a problem? Please describe.
VxWorks will invoke malloc() to obtain a stack for new tasks if the OS_TaskCreate() call is passed NULL for a stack pointer. This gets memory from the system heap which is not desirable for some users.

Describe the solution you'd like
Allow customization of the pool from which this memory is derived.

Describe alternatives you've considered
N/A

Additional context
Stakeholder request/need.

Requester Info
Joseph Hickey, Vantage Systems, Inc.
@jphickey jphickey self-assigned this May 24, 2024
jphickey added a commit to jphickey/osal that referenced this issue May 28, 2024
@jphickey
Fix nasa#1463, Implement separate allocator for task stacks
6fea765 
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 linked a pull request May 28, 2024 that will close this issue
Open
2 tasks
jphickey added a commit to jphickey/osal that referenced this issue May 28, 2024
@jphickey
Fix nasa#1463, Implement separate allocator for task stacks
40eb028 
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jphickey jphickey

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #1463, Implement separate allocator for task stacks jphickey/osal
1 participant
@jphickey