On Thu, Oct 10, 2024 at 05:58:10PM +0800, Baolin Wang wrote: > Considering that tmpfs already has the 'huge=' option to control the THP > allocation, it is necessary to maintain compatibility with the 'huge=' > option, as well as considering the 'deny' and 'force' option controlled > by '/sys/kernel/mm/transparent_hugepage/shmem_enabled'. No, it's not. No other filesystem honours these settings. tmpfs would not have had these settings if it were written today. It should simply ignore them, the way that NFS ignores the "intr" mount option now that we have a better solution to the original problem. To reiterate my position: - When using tmpfs as a filesystem, it should behave like other filesystems. - When using tmpfs to implement MAP_ANONYMOUS | MAP_SHARED, it should behave like anonymous memory. No more special mount options.
