On Wed, 30 Oct 2024 09:58:54 -0300 Maíra Canal <mcanal@xxxxxxxxxx> wrote: > The second and third patches focus on controlling THP support for shmem > via the kernel command line. The second patch introduces a parameter to > control the global default huge page allocation policy for the internal > shmem mount. The changelogs for patches 2 and 3 both say : By configuring ..., applications that use shmem, such as the DRM GEM objects, : can take advantage of mTHP before it's been configured through sysfs. There isn't a lot of info here - please explain this timing issue in more detail. Because the question which leaps to mind is: shouldn't the "applications that use shmem" be changed to "configure mTHP through sysfs" *before* "using shmem"? Seems pretty basic. Also, please consider my question to be a critique of the changelogs. If the changelogs were complete, I wouldn't need to ask any questions!
