Re: [PATCH v5 01/14] memory-hotplug: try to offline the memory twice to avoid dependence

2013-02-06 Thread Glauber Costa
On 02/06/2013 02:10 PM, Tang Chen wrote: > On 02/06/2013 05:17 PM, Tang Chen wrote: >> Hi all, >> >> On 02/06/2013 11:07 AM, Tang Chen wrote: >>> Hi Glauber, all, >>> >>> An old thing I want to discuss with you. :) >>> >>> On

Re: [PATCH v6 00/15] memory-hotplug: hot-remove physical memory

2013-01-10 Thread Glauber Costa
> If it's configure as ZONE_NORMAL, you need to pray for offlining memory. > > AFAIK, IBM's ppc? has 16MB section size. So, some of sections can be > offlined > even if they are configured as ZONE_NORMAL. For them, placement of offlined > memory is not important because it's virtualized by LPAR,

Re: [PATCH v6 00/15] memory-hotplug: hot-remove physical memory

2013-01-09 Thread Glauber Costa
On 01/10/2013 11:31 AM, Kamezawa Hiroyuki wrote: > (2013/01/10 16:14), Glauber Costa wrote: >> On 01/10/2013 06:17 AM, Tang Chen wrote: >>>>> Note: if the memory provided by the memory device is used by the >>>>> kernel, it >>>>> can't be

Re: [PATCH v6 00/15] memory-hotplug: hot-remove physical memory

2013-01-09 Thread Glauber Costa
On 01/10/2013 06:17 AM, Tang Chen wrote: >>> Note: if the memory provided by the memory device is used by the >>> kernel, it >>> can't be offlined. It is not a bug. >> >> Right. But how often does this happen in testing? In other words, >> please provide an overall description of how well memory

Re: [PATCH v5 01/14] memory-hotplug: try to offline the memory twice to avoid dependence

2013-01-09 Thread Glauber Costa
On 12/30/2012 09:58 AM, Wen Congyang wrote: > At 12/25/2012 04:35 PM, Glauber Costa Wrote: >> On 12/24/2012 04:09 PM, Tang Chen wrote: >>> From: Wen Congyang >>> >>> memory can't be offlined when CONFIG_MEMCG is selected. >>> For example: the

Re: [PATCH v5 01/14] memory-hotplug: try to offline the memory twice to avoid dependence

2012-12-25 Thread Glauber Costa
On 12/24/2012 04:09 PM, Tang Chen wrote: > From: Wen Congyang > > memory can't be offlined when CONFIG_MEMCG is selected. > For example: there is a memory device on node 1. The address range > is [1G, 1.5G). You will find 4 new directories memory8, memory9, memory10, > and memory11 under the dire

Re: [PATCH powerpc 2/2] kfree the cache name of pgtable cache if SLUB is used

2012-07-06 Thread Glauber Costa
On 07/05/2012 01:29 PM, Li Zhong wrote: > On Thu, 2012-07-05 at 12:23 +0400, Glauber Costa wrote: >> On 07/05/2012 05:41 AM, Li Zhong wrote: >>> On Wed, 2012-07-04 at 16:40 +0400, Glauber Costa wrote: >>>> On 07/04/2012 01:00 PM, Li Zhong wrote: >>>>>

Re: [PATCH SLAB 1/2 v3] duplicate the cache name in SLUB's saved_alias list, SLAB, and SLOB

2012-07-06 Thread Glauber Costa
On 07/06/2012 11:54 AM, Li Zhong wrote: > + if (!c && lname) > + kfree(lname); > + kfree can still be validly called with a NULL argument. No need for the lname in the conditional. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.o

Re: [PATCH powerpc 2/2] kfree the cache name of pgtable cache if SLUB is used

2012-07-05 Thread Glauber Costa
On 07/05/2012 05:41 AM, Li Zhong wrote: > On Wed, 2012-07-04 at 16:40 +0400, Glauber Costa wrote: >> On 07/04/2012 01:00 PM, Li Zhong wrote: >>> On Tue, 2012-07-03 at 15:36 -0500, Christoph Lameter wrote: >>>>> Looking through the emails it seems that there is

Re: [PATCH powerpc 2/2] kfree the cache name of pgtable cache if SLUB is used

2012-07-04 Thread Glauber Costa
On 07/04/2012 01:00 PM, Li Zhong wrote: > On Tue, 2012-07-03 at 15:36 -0500, Christoph Lameter wrote: >> > Looking through the emails it seems that there is an issue with alias >> > strings. > To be more precise, there seems no big issue currently. I just wanted to > make following usage of kmem_c

Re: [PATCH SLUB 1/2] duplicate the cache name in saved_alias list

2012-06-25 Thread Glauber Costa
On 06/25/2012 01:53 PM, Li Zhong wrote: SLUB duplicates the cache name in kmem_cache_create(). However if the cache could be merged to others during early booting, the name pointer is saved in saved_alias list, and the string needs to be kept valid before slab_sysfs_init() is called. This patch