[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20101005140835.9c80c2e7.kamezawa.hiroyu@jp.fujitsu.com>
Date: Tue, 5 Oct 2010 14:08:35 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: Nathan Fontenot <nfont@...tin.ibm.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linuxppc-dev@...ts.ozlabs.org, Greg KH <greg@...ah.com>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Robin Holt <holt@....com>, steiner@....com
Subject: Re: [PATCH 3/9] v3 Add section count to memory_block struct
On Fri, 01 Oct 2010 13:30:40 -0500
Nathan Fontenot <nfont@...tin.ibm.com> wrote:
> Add a section count property to the memory_block struct to track the number
> of memory sections that have been added/removed from a memory block. This
> allows us to know when the last memory section of a memory block has been
> removed so we can remove the memory block.
>
> Signed-off-by: Nathan Fontenot <nfont@...tin.ibm.com>
>
Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
a nitpick,
> Index: linux-next/include/linux/memory.h
> ===================================================================
> --- linux-next.orig/include/linux/memory.h 2010-09-29 14:56:29.000000000 -0500
> +++ linux-next/include/linux/memory.h 2010-09-30 14:13:50.000000000 -0500
> @@ -23,6 +23,8 @@
> struct memory_block {
> unsigned long phys_index;
> unsigned long state;
> + int section_count;
I prefer
int section_count; /* updated under mutex */
or some for this kind of non-atomic counters. but nitpick.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists