Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754471AbcK1SsP (ORCPT ); Mon, 28 Nov 2016 13:48:15 -0500 Received: from outbound-smtp09.blacknight.com ([46.22.139.14]:53665 "EHLO outbound-smtp09.blacknight.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754269AbcK1SsB (ORCPT ); Mon, 28 Nov 2016 13:48:01 -0500 Date: Mon, 28 Nov 2016 18:47:58 +0000 From: Mel Gorman To: Christoph Lameter Cc: Andrew Morton , Michal Hocko , Vlastimil Babka , Johannes Weiner , Linux-MM , Linux-Kernel Subject: Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v3 Message-ID: <20161128184758.bcz5ar5svv7whnqi@techsingularity.net> References: <20161127131954.10026-1-mgorman@techsingularity.net> <20161128162126.ulbqrslpahg4wdk3@techsingularity.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.2 (2016-07-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 802 Lines: 21 On Mon, Nov 28, 2016 at 10:38:58AM -0600, Christoph Lameter wrote: > > > that only insiders know how to tune and an overall fragile solution. > > While I agree with all of this, it's also a problem independent of this > > patch. > > It is related. The fundamental issue with fragmentation remain and IMHO we > really need to tackle this. > Fragmentation is one issue. Allocation scalability is a separate issue. This patch is about scaling parallel allocations of small contiguous ranges. Even if there were fragmentation-related patches up for discussion, they would not be directly affected by this patch. If you have a series aimed at parts of the fragmentation problem or how subsystems can avoid tracking 4K pages in some important cases then by all means post them. -- Mel Gorman SUSE Labs