Skip to content

Steal-able tasks/Task Queue + undefined behavior handler #62

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

Open
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

stevenqie
Copy link
Contributor

@stevenqie stevenqie commented May 6, 2025

This PR implements functionality for the task queue, functionality explained in the following docs: https://charm.readthedocs.io/en/latest/charm++/manual.html#stealable-tasks-for-within-node-load-balancing

There is also an example that tests this. PE0 calls and pushes K tasks to its own task queue. Other PE's should steal from PE0 because they see that their task queue is empty. In the end, we should see an about equal distribution of tasksExecuted by each PE.

Also added an undefined handler, which gets initialized to index 0. Assuming that when a user creates a message and the memory get's memset to 0, not providing a handlerID will result in an error message saying " Possible undefined handler called. Please check to see if you've populated the handlerId field of your message."

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

Successfully merging this pull request may close these issues.

2 participants