Re: [Xen-devel] [PATCH 3/3] drivers/xen/balloon.c: Xen memory balloon driver with memory hotplug support

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Daniel Kiper
Date: Wednesday, December 29, 2010 - 9:42 am

Hi,

On Mon, Dec 27, 2010 at 10:25:49AM -0500, Konrad Rzeszutek Wilk wrote:

If release_resource()/adjust_resource() fail it means
there is no possibility to align resource descpription with
real memory address space. I think it is fatal error. If
we decide to leave system in that state it could lead
to data corruption or crash.


Very good question. I based that fragment of code on original
increase_reservation()/decrease_reservation(). I attempted to find
any good explanation for that however, without success. That is why
I decided to not touch that fragment of code. If I had any
good argument to change that I will do that.


Yes, request_additional_memory() allocate memory in chunks
and r is used between subsequent calls until all memory
is allocated.


If balloon_stats.mh_policy == MH_POLICY_TRY_UNTIL_SUCCESS then
balloon process attempt to allocate requested memory until success.
*r is freed only when any error appears and no memory is allocated.


Please look above.


Memory is onlined only when all of it is allocated.


Daniel
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [Xen-devel] [PATCH 3/3] drivers/xen/balloon.c: Xen mem ..., Konrad Rzeszutek Wilk, (Mon Dec 27, 8:25 am)
Re: [Xen-devel] [PATCH 3/3] drivers/xen/balloon.c: Xen mem ..., Daniel Kiper, (Wed Dec 29, 9:42 am)