On Tue, Dec 02, 2014 at 02:29:15PM -0800, K. Y. Srinivasan wrote: > We currently release memory (balloon down) in the interrupt context and we also > post memory status while releasing memory. Rather than posting the status > in the interrupt context, wakeup the status posting thread to post the status. > This will address the inconsistent lock state that Sitsofe Wheeler <sitsofe@xxxxxxxxx> > reported: Sorry I didn't follow up on this. Things looked better after the patch but I was seeing a strange issue where the memory was being reduced to some minimum and the balloon would never shrink so the available memory was seemingly locked from then on. I ran out of time to investigate this later behaviour and didn't have the time to check if it had always been the case but I think I see other patches saying you nailed it and other issues. Do you have a published git tree with all these pieces in or have they already been mainlined? -- Sitsofe | http://sucs.org/~sits/ _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
