-
Notifications
You must be signed in to change notification settings - Fork 218
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
Async / executer #501
Comments
As we don't have async support in rp-hal yet, the question of how the schedule async tasks to both cores isn't the most pressing one. If you are interested in async rust on the rp2040, it's probably worth to have a look at https://github.com/embassy-rs/embassy. However, I have no idea if they have multi-core support. |
In fact, I am interested in concurrent execution on the cores without the need of an OS. |
For what it's worth, I am running a nostd_async executor on each core on wilskeeb. Tasks don't get passed from one core to the other because that'd involve some extra requirement that I didn't want to spend time on. Each executor is able to run several tasks in "parallel" (that's the whole point of async). |
Am I wrong assuming, that by "async fn" and "future" in principle any type of real or virtual parallelism can be handled, and it depends on the executor (using an OS, if present) which kind is in charge (e.g. single core scheduler, SMP, or - e.g. with 2040 (without OS and low complexity executor) , dual core (limited to two tasks) ? |
In this context: async gets you concurrency, not parallelism. |
As the dual core paradigm is one of the key features of the Pico / 2040, Rust support would need to allow for async fn to be executed in parallel without introducing an operation system in the project but by simply distributing the tasks to the two cores with the "executer".
Is there already anything planned with such a goal ?
Thanks a lot for listening,
-Michael
The text was updated successfully, but these errors were encountered: