[Sync-En] opcache: document huge page use by the shared memory segment - #1313
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Translation of php/doc-en#4861 (commit 83c44e1): opcache.memory_consumption now explains that the shared memory segment also holds the JIT buffer and is allocated on huge pages when available, and opcache.huge_code_pages says it only remaps the text segment. EN-Revision updated.
Also fixed several defects in the same file along the way: stale TODO comments and a leftover English sentence, a few mistranslations (file_cache_fallback, revalidate_path, the JIT recursion limits) and some table cells that differed from the English.
Fixes: #1293