I noticed that it only enables huge-code-pages feature support by using "--enable-opcache --enable-opcache-file --enable-huge-code-pages" options when building php extensions as below shows.
ext_config='--prefix=/usr --enable-cli ... --enable-opcache --enable-opcache-file --enable-huge-code-pages'
For other components, like fpm, it doesn't use the above options, and "--diable-all" option explicitly excluded all features that are included by default. In this case, the code supporting huge-code-pages are not included in php binary. So user cannot enable it in runtime, even with "opcache.huge_code_pages=1" config in php.ini.
I know huge_code_pages feature is still experimental, so it's disabled by design? How about include that feature and let use to control whether enable it or not?
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
This is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix automatically.
Would you mind filing a bug with Debian please? If you do so please add a link to the bug here.