enable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS

[hargar19]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Enable the CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS config for x86 builds. This modification will enhance performance for workloads running on A100 nodes. Below is a comparison of superbench results (with the proposed configuration change) between AzureLinux 3.0 and Ubuntu v6.5 on an A100 node

This change will enable the Singularity team to move to AzureLinux 3.0 kernel for GA.

Change Log

CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is enabled for x86 builds.

Does this affect the toolchain?

No

Associated issues

https://microsoft.visualstudio.com/OS/_workitems/edit/54614523/
Investigate kernel config differences between L1 VM AzureLinux 3.0 vs L1 Ubuntu 20.04 kernel 6.5 to achieve runtime performance parity on Superbench.

Test Methodology

Kernel is built locally and tested on A100 node with Superbench