Yes, I agree. For our case, we have tens of GB files and thp with page cache does improve the number as expected. And compared to hugetlbfs (static huge page), it's more flexible and beneficial to the system wide .... Best wishes, -- Ning Qu (曲宁) | Software Engineer | quning@xxxxxxxxxx | +1-408-418-6066 On Mon, Sep 30, 2013 at 8:27 AM, Dave Hansen <dave@xxxxxxxx> wrote: > On 09/30/2013 03:02 AM, Mel Gorman wrote: >> I am afraid I never looked too closely once I learned that the primary >> motivation for this was relieving iTLB pressure in a very specific >> case. AFAIK, this is not a problem in the vast majority of modern CPUs >> and I found it very hard to be motivated to review the series as a result. >> I suspected that in many cases that the cost of IO would continue to dominate >> performance instead of TLB pressure. I also found it unlikely that there >> was a workload that was tmpfs based that used enough memory to be hurt >> by TLB pressure. My feedback was that a much more compelling case for the >> series was needed but this discussion all happened on IRC unfortunately. > > FWIW, I'm mostly intrigued by the possibilities of how this can speed up > _software_, and I'm rather uninterested in what it can do for the TLB. > Page cache is particularly painful today, precisely because hugetlbfs > and anonymous-thp aren't available there. If you have an app with > hundreds of GB of files that it wants to mmap(), even if it's in the > page cache, it takes _minutes_ to just fault in. One example: > > https://lkml.org/lkml/2013/6/27/698 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href