25.3.6 Backport of #79147: Remove guard pages from fibers and alternative stack for signals in threads #917
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Better guard pages with MADV_GUARD_INSTALL/MADV_GUARD_REMOVE (linux 6.13+)
…ack-protection stack allocation in Fiber and alternative stack for signals
…-alt-thread fix ThreadStack::getSize
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Remove guard pages for threads and async_socket_for_remote/use_hedge_requests. Change the allocation method in
FiberStackfrommmaptoaligned_alloc. Since this splits VMAs and under heavy load vm.max_map_count can be reached. (ClickHouse#78423 by @azat, ClickHouse#79147 and ClickHouse#79533 by @CheSema)Exclude tests: