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

core: reactor_config: add reserve_io_control_blocks #2533

Merged
merged 1 commit into from
Nov 13, 2024

Conversation

denesb
Copy link
Contributor

@denesb denesb commented Nov 11, 2024

This new option allows reserving the configured amount of IOCBs, so they are available to a side application running in parallell to the seastar application.
The use case is ScyllaDB and its tool applications, both ScyllaDB and its tool applications need IOCBs to run, so ScyllaDB has to be able to tell seastar to reserve some IOCBs for the tools as well.

@yaronkaikov
Copy link

Who should review this? @denesb

@denesb
Copy link
Contributor Author

denesb commented Nov 12, 2024

Who should review this? @denesb

@avikivity would be the best candidate, since he was part of the discussion from which this patch was born (scylladb/scylladb#19185).
But strictly speaking any @scylladb/seastar-maint member can review it.

src/core/reactor.cc Outdated Show resolved Hide resolved
@denesb
Copy link
Contributor Author

denesb commented Nov 13, 2024

New in v2: ensure available_aio doesn't underflow.

This new option allows reserving the configured amount of IOCBs, so they
are available to a side application running in parallell to the seastar
application.
The use case is ScyllaDB and its tool applications, both ScyllaDB and
its tool applications need IOCBs to run, so ScyllaDB has to be able to
tell seastar to reserve some IOCBs for the tools as well.
@avikivity avikivity merged commit c5f9e3a into scylladb:master Nov 13, 2024
15 checks passed
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.

3 participants