Repository navigation
Conversation
arnaud-lb
force-pushed
the
opcache-shm-pkey
branch
from
October 23, 2026 13:34
c2334a3 to
eb5629c
Compare
arnaud-lb
force-pushed
the
opcache-shm-pkey
branch
from
October 23, 2026 14:14
eb5629c to
628ea72
Compare
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
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.
Same as #20461, but OPcache-only since we can't disable execution on x86_64.
This uses pkeys to make the OPcache mapping readonly when we are not updating it, when
opcache.protect_memoryis on.The should accelerate
opcache.protect_memoryCI builds. The overhead is small enough to be used in production, too (<1%).See