> On Aug 5, 2022, at 12:40, alexlzhu@xxxxxx wrote: > > From: Alexander Zhu <alexlzhu@xxxxxx> > > This change introduces a tool that scans through all of physical > memory for anonymous THPs and groups them into buckets based > on utilization. Out of curiosity, do you have any statistics on how much of a performance impact scanning may have? We've reached the point where we've finally been able to show previous admonitions to not enable THP due to a negative performance impact no longer hold true, and I'd hate to see systems on which enabling THP now would cause a performance hit due to this scanner.