Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758945Ab3EAWjh (ORCPT ); Wed, 1 May 2013 18:39:37 -0400 Received: from mail-pa0-f45.google.com ([209.85.220.45]:37459 "EHLO mail-pa0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757608Ab3EAWjf (ORCPT ); Wed, 1 May 2013 18:39:35 -0400 Date: Wed, 1 May 2013 15:39:33 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Cody P Schafer cc: Andrew Morton , Linux MM , LKML Subject: Re: [PATCH 1/4] mmzone: make holding lock_memory_hotplug() a requirement for updating pgdat size In-Reply-To: <518197E2.7050004@linux.vnet.ibm.com> Message-ID: References: <1367446635-12856-1-git-send-email-cody@linux.vnet.ibm.com> <1367446635-12856-2-git-send-email-cody@linux.vnet.ibm.com> <518197E2.7050004@linux.vnet.ibm.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 693 Lines: 17 On Wed, 1 May 2013, Cody P Schafer wrote: > They are also initialized at boot without pgdat_resize_lock(), if we consider > boot time, quite a few of the statements on when locking is required are > wrong. > > That said, you are correct that it is not strictly required to hold > lock_memory_hotplug() when updating the fields in question because > pgdat_resize_lock() is used. > I think you've confused node size fields with zone size fields. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/