Skip to content

CP-49141: mark the DB lock as high priority #6180

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

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

edwintorok
Copy link
Contributor

Builds on top of #6177 and #6179, the commit new in this PR is CP-49141.

@edwintorok edwintorok changed the base branch from feature/perf to master February 4, 2025 17:17
@edwintorok edwintorok force-pushed the pr/CP-49141 branch 2 times, most recently from cfedebc to 4d952e6 Compare February 4, 2025 17:19
@edwintorok edwintorok marked this pull request as ready for review February 4, 2025 17:20
@edwintorok
Copy link
Contributor Author

The XAPI timeslice code is disabled by default, so this won't yet have an effect. The 2 functions called here (acquired/released) sets a global Atomic value, and has no other effect, so there is no separate feature flag for this one.

…hread.yield while we hold it

We'd still yield when the tick thread yields, or on syscalls.

Signed-off-by: Edwin Török <edwin.torok@cloud.com>
@edwintorok edwintorok enabled auto-merge February 4, 2025 17:58
@edwintorok edwintorok added this pull request to the merge queue Feb 4, 2025
Merged via the queue into xapi-project:master with commit c2d99cd Feb 4, 2025
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