From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756101AbbJHUUl (ORCPT ); Thu, 8 Oct 2015 16:20:41 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:38119 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753615AbbJHUUj (ORCPT ); Thu, 8 Oct 2015 16:20:39 -0400 Date: Thu, 8 Oct 2015 13:20:37 -0700 From: Andrew Morton To: David Rientjes Cc: "Patil, Kiran" , Jiang Liu , Mel Gorman , Mike Galbraith , Peter Zijlstra , "Wysocki, Rafael J" , Tang Chen , Tejun Heo , "Kirsher, Jeffrey T" , "Brandeburg, Jesse" , "Nelson, Shannon" , "Wyborny, Carolyn" , "Skidmore, Donald C" , "Vick, Matthew" , "Ronciak, John" , "Williams, Mitch A" , "Luck, Tony" , "netdev@vger.kernel.org" , "x86@kernel.org" , "linux-hotplug@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "intel-wired-lan@lists.osuosl.org" Subject: Re: [Intel-wired-lan] [Patch V3 5/9] i40e: Use numa_mem_id() to better support memoryless node Message-Id: <20151008132037.fc3887da0818e7d011cb752f@linux-foundation.org> In-Reply-To: References: <1439781546-7217-1-git-send-email-jiang.liu@linux.intel.com> <1439781546-7217-6-git-send-email-jiang.liu@linux.intel.com> <4197C471DCF8714FBA1FE32565271C148FFFF4D3@ORSMSX103.amr.corp.intel.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 19 Aug 2015 17:18:15 -0700 (PDT) David Rientjes wrote: > On Wed, 19 Aug 2015, Patil, Kiran wrote: > > > Acked-by: Kiran Patil > > Where's the call to preempt_disable() to prevent kernels with preemption > from making numa_node_id() invalid during this iteration? David asked this question twice, received no answer and now the patch is in the maintainer tree, destined for mainline. If I was asked this question I would respond The use of numa_mem_id() is racy and best-effort. If the unlikely race occurs, the memory allocation will occur on the wrong node, the overall result being very slightly suboptimal performance. The existing use of numa_node_id() suffers from the same issue. But I'm not the person proposing the patch. Please don't just ignore reviewer comments!