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

Consider having next_notification also return the size of the next notification #403

Open
tomaka opened this issue Apr 15, 2020 · 1 comment
Labels
A-core Issues concerning the core

Comments

@tomaka
Copy link
Owner

tomaka commented Apr 15, 2020

At the moment, here's what a process does to receive a notification:

  • The process pre-allocates some buffer to receive the notification.
  • We call next_notification and jump to the kernel.
  • If the notification is large than the pre-allocated buffer, we return an error plus the required buffer size.
  • The process then allocates a large-enough buffer and call next_notification.

If right after we want to receive the next notification, we have to do a pre-allocation again and try again.

It would be more efficient if the kernel immediately returned as well the size of the next notification that the call would have returned, in order to skip that step the next time.

@tomaka tomaka added the A-core Issues concerning the core label Apr 15, 2020
@tomaka
Copy link
Owner Author

tomaka commented Mar 16, 2021

cc #863

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-core Issues concerning the core
Projects
None yet
Development

No branches or pull requests

1 participant