On Fri, 2015-03-06 at 09:52 +, Stefano Stabellini wrote:
On Fri, 6 Mar 2015, Ian Campbell wrote:
On Thu, 2015-03-05 at 21:08 -0700, Mike Latimer wrote:
On Thursday, March 05, 2015 05:49:35 PM Ian Campbell wrote:
On Tue, 2015-03-03 at 11:08 +, Stefano Stabellini wrote:
Hi
On Fri, 6 Mar 2015, Ian Campbell wrote:
On Fri, 2015-03-06 at 09:52 +, Stefano Stabellini wrote:
On Fri, 6 Mar 2015, Ian Campbell wrote:
On Thu, 2015-03-05 at 21:08 -0700, Mike Latimer wrote:
On Thursday, March 05, 2015 05:49:35 PM Ian Campbell wrote:
On Tue, 2015-03-03 at 11:08
On Fri, 6 Mar 2015, Ian Campbell wrote:
On Thu, 2015-03-05 at 21:08 -0700, Mike Latimer wrote:
On Thursday, March 05, 2015 05:49:35 PM Ian Campbell wrote:
On Tue, 2015-03-03 at 11:08 +, Stefano Stabellini wrote:
Hi all,
this patch series fixes the freemem loop on machines
On Thu, 2015-03-05 at 21:08 -0700, Mike Latimer wrote:
On Thursday, March 05, 2015 05:49:35 PM Ian Campbell wrote:
On Tue, 2015-03-03 at 11:08 +, Stefano Stabellini wrote:
Hi all,
this patch series fixes the freemem loop on machines with very large
amount of memory, where the
On Fri, 2015-03-06 at 10:22 +, Stefano Stabellini wrote:
On Fri, 6 Mar 2015, Ian Campbell wrote:
On Fri, 2015-03-06 at 09:52 +, Stefano Stabellini wrote:
On Fri, 6 Mar 2015, Ian Campbell wrote:
On Thu, 2015-03-05 at 21:08 -0700, Mike Latimer wrote:
On Thursday, March 05,
Stefano Stabellini wrote:
On Fri, 6 Mar 2015, Ian Campbell wrote:
This is missing my point.
We need to consider the case of a modified libvirt with the old, broken,
libxl too.
For that case, we might want to make sure that the new timeout passed to
libxl_wait_for_memory_target is
On Tue, 2015-03-03 at 11:08 +, Stefano Stabellini wrote:
Hi all,
this patch series fixes the freemem loop on machines with very large
amount of memory, where the current wait time is not enough.
In order to be able to handle arbitrarly large amount of ram, we
implement in
On Thursday, March 05, 2015 05:49:35 PM Ian Campbell wrote:
On Tue, 2015-03-03 at 11:08 +, Stefano Stabellini wrote:
Hi all,
this patch series fixes the freemem loop on machines with very large
amount of memory, where the current wait time is not enough.
In order to be able to
On Tuesday, March 03, 2015 02:54:50 PM Mike Latimer wrote:
Thanks for all the help and patience as we've worked through this. Ack to
the whole series:
Acked-by: Mike Latimer mlati...@suse.com
I guess the more correct response is:
Reviewed-by: Mike Latimer mlati...@suse.com
Tested-by:
Hi all,
this patch series fixes the freemem loop on machines with very large
amount of memory, where the current wait time is not enough.
In order to be able to handle arbitrarly large amount of ram, we
implement in libxl_wait_for_memory_target a policy of waiting until dom0
is making progress.
On Tuesday, March 03, 2015 11:08:38 AM Stefano Stabellini wrote:
Hi all,
this patch series fixes the freemem loop on machines with very large
amount of memory, where the current wait time is not enough.
In order to be able to handle arbitrarly large amount of ram, we
implement in
11 matches
Mail list logo
