From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266615AbUFYUqB (ORCPT ); Fri, 25 Jun 2004 16:46:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266695AbUFYUqB (ORCPT ); Fri, 25 Jun 2004 16:46:01 -0400 Received: from fujitsu2.fujitsu.com ([192.240.0.2]:61625 "EHLO fujitsu2.fujitsu.com") by vger.kernel.org with ESMTP id S266615AbUFYUpv (ORCPT ); Fri, 25 Jun 2004 16:45:51 -0400 Date: Fri, 25 Jun 2004 13:45:30 -0700 From: Yasunori Goto To: Dave Hansen Subject: Re: [Lhms-devel] Re: Merging Nonlinear and Numa style memory hotplug Cc: Linux Kernel ML , Linux Hotplug Memory Support , Linux-Node-Hotplug , linux-mm , "BRADLEY CHRISTIANSEN [imap]" In-Reply-To: <1088189973.29059.231.camel@nighthawk> References: <20040625114720.2935.YGOTO@us.fujitsu.com> <1088189973.29059.231.camel@nighthawk> Message-Id: <20040625121110.2937.YGOTO@us.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.07.02 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > Are you sure that all architectures need phys_section? > > You don't *need* it, but the alternative is a scan of the mem_section[] > array, which would be much, much slower. > > Do you have an idea for an alternate implementation? I didn't find that scan of the mem_section[] is necessary. I thought just that mem_section index = phys_section index. May I ask why scan of mem_section is necessary? I might still have misunderstood something. -- Yasunori Goto From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fujitsu2.fujitsu.com (localhost [127.0.0.1]) by fujitsu2.fujitsu.com (8.12.10/8.12.9) with ESMTP id i5PKjkNv027558 for ; Fri, 25 Jun 2004 13:45:46 -0700 (PDT) Date: Fri, 25 Jun 2004 13:45:30 -0700 From: Yasunori Goto Subject: Re: [Lhms-devel] Re: Merging Nonlinear and Numa style memory hotplug In-Reply-To: <1088189973.29059.231.camel@nighthawk> References: <20040625114720.2935.YGOTO@us.fujitsu.com> <1088189973.29059.231.camel@nighthawk> Message-Id: <20040625121110.2937.YGOTO@us.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Dave Hansen Cc: Linux Kernel ML , Linux Hotplug Memory Support , Linux-Node-Hotplug , linux-mm , "BRADLEY CHRISTIANSEN [imap]" List-ID: > > Are you sure that all architectures need phys_section? > > You don't *need* it, but the alternative is a scan of the mem_section[] > array, which would be much, much slower. > > Do you have an idea for an alternate implementation? I didn't find that scan of the mem_section[] is necessary. I thought just that mem_section index = phys_section index. May I ask why scan of mem_section is necessary? I might still have misunderstood something. -- Yasunori Goto -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org