On Thu, Jul 15, 2021 at 04:34:46AM +0100, Matthew Wilcox (Oracle) wrote: > Managing memory in 4KiB pages is a serious overhead. Many benchmarks > benefit from a larger "page size". As an example, an earlier iteration > of this idea which used compound pages (and wasn't particularly tuned) > got a 7% performance boost when compiling the kernel. I want to thank Michael Larabel for his benchmarking effort: https://www.phoronix.com/scan.php?page=news_item&px=Folios-v14-Testing-AMD-Linux I'm not too surprised by the lack of performance change on the majority of benchmarks. This patch series is only going to change things for heavy users of the page cache (ie it'll do nothing for anon memory users), and it's only really a benefit for programs that have good locality. What blows me away is the 80% performance improvement for PostgreSQL. I know they use the page cache extensively, so it's plausibly real. I'm a bit surprised that it has such good locality, and the size of the win far exceeds my expectations. We should probably dive into it and figure out exactly what's going on. Should we accelerate inclusion of this patchset? Right now, I have 89 mm patches queued up for the 5.15 merge window. My plan was to get the 17 iomap + block patches, plus another 18 page cache patches into 5.16 and then get the 14 multi-page folio patches into 5.17. But I'm mindful of the longterm release coming up "soon", and I'm not sure we're best served by multiple distros trying to backport the multi-page folio patches to either 5.15 or 5.16.
