Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754999Ab2HaUuA (ORCPT ); Fri, 31 Aug 2012 16:50:00 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:50521 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751855Ab2HaUt6 (ORCPT ); Fri, 31 Aug 2012 16:49:58 -0400 Date: Fri, 31 Aug 2012 13:49:56 -0700 From: Andrew Morton To: wency@cn.fujitsu.com Cc: x86@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, linux-ia64@vger.kernel.org, cmetcalf@tilera.com, sparclinux@vger.kernel.org, rientjes@google.com, liuj97@gmail.com, len.brown@intel.com, benh@kernel.crashing.org, paulus@samba.org, cl@linux.com, minchan.kim@gmail.com, kosaki.motohiro@jp.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com Subject: Re: [RFC v8 PATCH 00/20] memory-hotplug: hot-remove physical memory Message-Id: <20120831134956.fec0f681.akpm@linux-foundation.org> In-Reply-To: <1346148027-24468-1-git-send-email-wency@cn.fujitsu.com> References: <1346148027-24468-1-git-send-email-wency@cn.fujitsu.com> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.20.1; 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 Content-Length: 1329 Lines: 34 On Tue, 28 Aug 2012 18:00:07 +0800 wency@cn.fujitsu.com wrote: > This patch series aims to support physical memory hot-remove. Have you had much review and testing feedback yet? > The patches can free/remove the following things: > > - acpi_memory_info : [RFC PATCH 4/19] > - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19] > - iomem_resource : [RFC PATCH 9/19] > - mem_section and related sysfs files : [RFC PATCH 10-11, 13-16/19] > - page table of removed memory : [RFC PATCH 12/19] > - node and related sysfs files : [RFC PATCH 18-19/19] > > If you find lack of function for physical memory hot-remove, please let me > know. I doubt if many people have hardware which permits physical memory removal? How would you suggest that people with regular hardware can test these chagnes? > Known problems: > 1. memory can't be offlined when CONFIG_MEMCG is selected. That's quite a problem! Do you have a description of why this is the case, and a plan for fixing it? -- 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/