We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Timeouts can be very frequent, and each timeout is malloced and later freed, which is a rather expensive op. See https://github.com/gramineproject/gramine-tdx/blob/intel_tdx/pal/src/host/vm-common/kernel_time.c, functions register_timeout() and deregister_timeout().
register_timeout()
deregister_timeout()
Instead, we can re-use the timeout objects, similarly to how we re-use thread stacks.
Timeouts are extensively used in futex() syscalls. And futex syscalls may be very frequent.
futex()
We may implement this optimization, but need to first make sure it can be a real bottleneck.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description of the feature
Timeouts can be very frequent, and each timeout is malloced and later freed, which is a rather expensive op. See https://github.com/gramineproject/gramine-tdx/blob/intel_tdx/pal/src/host/vm-common/kernel_time.c, functions
register_timeout()
andderegister_timeout()
.Instead, we can re-use the timeout objects, similarly to how we re-use thread stacks.
Why Gramine should implement it?
Timeouts are extensively used in
futex()
syscalls. And futex syscalls may be very frequent.We may implement this optimization, but need to first make sure it can be a real bottleneck.
The text was updated successfully, but these errors were encountered: