RE: [PATCH v7 1/8] Talitos: Support for async_tx XOR offload

2012-08-31 Thread Geanta Neag Horia Ioan-B05471
On Fri, 31 Aug 2012 06:08:05 +0300, Liu Qiang-B32616 b32...@freescale.com wrote: -Original Message- From: Geanta Neag Horia Ioan-B05471 Sent: Thursday, August 30, 2012 10:23 PM To: Liu Qiang-B32616; linux-cry...@vger.kernel.org; dan.j.willi...@gmail.com;

RE: [PATCH v7 1/8] Talitos: Support for async_tx XOR offload

2012-08-31 Thread Liu Qiang-B32616
-Original Message- From: Geanta Neag Horia Ioan-B05471 Sent: Friday, August 31, 2012 6:39 PM To: Liu Qiang-B32616; linux-cry...@vger.kernel.org; dan.j.willi...@gmail.com; herb...@gondor.hengli.com.au; da...@davemloft.net; linux-ker...@vger.kernel.org; linuxppc- d...@lists.ozlabs.org

Re: [RFC v8 PATCH 00/20] memory-hotplug: hot-remove physical memory

2012-08-31 Thread Andrew Morton
On Tue, 28 Aug 2012 18:00:07 +0800 we...@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]

Re: [RFC v8 PATCH 04/20] memory-hotplug: offline and remove memory when removing the memory device

2012-08-31 Thread Andrew Morton
On Tue, 28 Aug 2012 18:00:11 +0800 we...@cn.fujitsu.com wrote: +int remove_memory(int nid, u64 start, u64 size) +{ + int ret = -EBUSY; + lock_memory_hotplug(); + /* + * The memory might become online by other task, even if you offine it. + * So we check whether the

Re: [RFC v8 PATCH 08/20] memory-hotplug: remove /sys/firmware/memmap/X sysfs

2012-08-31 Thread Andrew Morton
On Tue, 28 Aug 2012 18:00:15 +0800 we...@cn.fujitsu.com wrote: From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type} sysfs files are created. But there is no code to remove these files. The patch implements the

Re: [RFC v8 PATCH 13/20] memory-hotplug: check page type in get_page_bootmem

2012-08-31 Thread Andrew Morton
On Tue, 28 Aug 2012 18:00:20 +0800 we...@cn.fujitsu.com wrote: From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com There is a possibility that get_page_bootmem() is called to the same page many times. So when get_page_bootmem is called to the same page, the function only increments