Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935444AbcJZWJ6 (ORCPT ); Wed, 26 Oct 2016 18:09:58 -0400 Received: from mail-oi0-f49.google.com ([209.85.218.49]:36822 "EHLO mail-oi0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755146AbcJZWJm (ORCPT ); Wed, 26 Oct 2016 18:09:42 -0400 MIME-Version: 1.0 In-Reply-To: <20161026220339.GE2699@techsingularity.net> References: <20161026203158.GD2699@techsingularity.net> <20161026220339.GE2699@techsingularity.net> From: Linus Torvalds Date: Wed, 26 Oct 2016 15:09:41 -0700 X-Google-Sender-Auth: h8tfN5T1psUGuvUoiHHuqxXlQhs Message-ID: Subject: Re: CONFIG_VMAP_STACK, on-stack struct, and wake_up_bit To: Mel Gorman Cc: Andy Lutomirski , Andreas Gruenbacher , Peter Zijlstra , Andy Lutomirski , LKML , Bob Peterson , Steven Whitehouse , linux-mm Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 526 Lines: 13 On Wed, Oct 26, 2016 at 3:03 PM, Mel Gorman wrote: > > To be clear, are you referring to PeterZ's patch that avoids the lookup? If > so, I see your point. Yup, that's the one. I think you tested it. In fact, I'm sure you did, because I remember seeing performance numbers from you ;) So yes, I'd expect my patch on its own to quite possibly regress on NUMA systems (although I wonder how much), but I consider PeterZ's patch the fix to that, so I wouldn't worry about it. Linus