On 10/17/18 8:33 AM, Aaron Lu wrote: > Profile on Intel Skylake server shows the most time consuming part > under zone->lock on allocation path is accessing those to-be-returned > page's "struct page" on the free_list inside zone->lock. One explanation > is, different CPUs are releasing pages to the head of free_list and > those page's 'struct page' may very well be cache cold for the allocating > CPU when it grabs these pages from free_list' head. The purpose here > is to avoid touching these pages one by one inside zone->lock. What about making the pages cache-hot first, without zone->lock, by traversing via page->lru. It would need some safety checks obviously (maybe based on page_to_pfn + pfn_valid, or something) to make sure we only read from real struct pages in case there's some update racing. The worst case would be not populating enough due to race, and thus not gaining the performance when doing the actual rmqueueing under lock. Vlastimil
