From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752549AbcLGOyd (ORCPT ); Wed, 7 Dec 2016 09:54:33 -0500 Received: from resqmta-ch2-06v.sys.comcast.net ([69.252.207.38]:37996 "EHLO resqmta-ch2-06v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751905AbcLGOyc (ORCPT ); Wed, 7 Dec 2016 09:54:32 -0500 Date: Wed, 7 Dec 2016 08:52:27 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@east.gentwo.org To: Mel Gorman cc: Andrew Morton , Michal Hocko , Vlastimil Babka , Johannes Weiner , Jesper Dangaard Brouer , Joonsoo Kim , Linux-MM , Linux-Kernel Subject: Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 In-Reply-To: <20161207101228.8128-1-mgorman@techsingularity.net> Message-ID: References: <20161207101228.8128-1-mgorman@techsingularity.net> Content-Type: text/plain; charset=US-ASCII X-CMAE-Envelope: MS4wfOzAMu76a7fHd7LcBHRWtNB/g72QGAmWkRCxg//bNtSWN7IM6crB82fBK8O0Jlw2EBQ9yPj5JZiGU+GaOQQdktqV86XX7qrcdVturhF4OmFHzCYZPU0x LfPI4nyBLl4D3oQBn1w6hIHALb5Qz3whaxsZIjQ0B77/OTH2EUXOa7bfP71ZBqvc2bqmHM9SzyUgNypPBxkQiSqztGpK8fM4F0Hd9wmNONR1clr1LbWvCKDr PX3Eq2qYpA1Xa9furcBZXu+qLIiTJekMr78DnIUTzSOh4qDcyLQ3ZbHDi9RjBDdmsnt9DZbd76My/eZg9MmPRjqoq3HmTUBimiBneFe4+tELZsOjLcMBXSgT DsUpKvgheCH9S3t5X70Thyeg3CSqOcqxUc278diDjQLEMwo6OqcNyyPo5r7P25OxKWqCJ/gS Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 7 Dec 2016, Mel Gorman wrote: > SLUB has been the default small kernel object allocator for quite some time > but it is not universally used due to performance concerns and a reliance > on high-order pages. The high-order concerns has two major components -- SLUB does not rely on high order pages. It falls back to lower order if the higher orders are not available. Its a performance concern. This is also an issue for various other kernel subsystems that really would like to have larger contiguous memory area. We are often seeing performance constraints due to the high number of 4k segments when doing large scale block I/O f.e. Otherwise I really like what I am seeing here.