[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [OSSTEST PATCH 8/9] mg-allocate: Better error handling when no candidates

On Thu, 2015-12-17 at 17:06 +0000, Ian Jackson wrote:
> Spot when our db search revealed no candidates for the resources to
> allocate, and:
> Â- when doing an immediate allocation, call it an error
> Â- when doing a planned allocation, cause it to prevent allocation
> ÂÂÂon this iteration, and print a suitably unreassuring message
> Previously it would simply say `nothing available'.
> Implement this as follows:
> Â- Report lack of candidates as $ok=-1 from alloc_1rescand
> Â- In alloc_1res, return this -1 as with any non-zero $ok
> Â- Handle the new $ok at all the call sites, in particular
> Â- In plan(), rename `allok' to `worstok' and have it be
> ÂÂÂthe worst relevant $ok value.ÂÂIf $ok gives -1, return
> ÂÂÂundef, rather than a booking list, to the allocator core.
> Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>

Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.