[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <EA08C942-E156-410D-8ADA-7A4812B20221@kernel.crashing.org>
Date: Thu, 27 Mar 2008 21:40:52 -0500
From: Kumar Gala <galak@...nel.crashing.org>
To: Badari Pulavarty <pbadari@...ibm.com>
Cc: lkml <linux-kernel@...r.kernel.org>, linuxppc-dev@...abs.org,
Andrew Morton <akpm@...ux-foundation.org>, paulus@...ba.org,
Yasunori Goto <y-goto@...fujitsu.com>
Subject: Re: [PATCH 4/5] [PPC] update lmb for hotplug memory add/remove
On Mar 27, 2008, at 7:39 PM, Badari Pulavarty wrote:
> ppc kernel maintains information about logical memory blocks in
> lmb.memory structure at the boot time. Its not updated for
> hotplug memory add/remove. hotplug memory notifier for memory
> add/remove now updates lmb.memory.
>
> This information is useful for eHEA driver to find out the memory
> layout and holes.
>
> NOTE: No special locking is needed for lmb_add() and lmb_remove().
> Calls to these are serialized by caller. (pSeries_reconfig_chain).
>
> Signed-off-by: Badari Pulavarty <pbadari@...ibm.com>
> ---
> arch/powerpc/platforms/pseries/hotplug-memory.c | 43 +++++++++++++++
> include/linux/lmb.h | 3 -
> lib/lmb.c | 66 ++++++++++++++
> ++++++----
> 3 files changed, 102 insertions(+), 10 deletions(-)
How is lmb_remove different than lmb_alloc?
- k
--
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