[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] RE: [PATCH][BALLOON] Fix minimum target
> ballooning on other systems then I think we'll have to wait for someone > to implement a more dynamic scheme (e.g., by hooking off the > OOM/low-memory paths, or by slowly allocating memory only when we can > see a reasonable amount of pages available on the free lists). >From the little code reading I have done, your second option seems better. Once the code goes down the OOM path the system is already in a shaky unstable state. The balloon driver has to be made to back off way before that. I have been meaning to try and look into this. I will try and do so. > I'm rather doubtful that a really good static estimate can be derived, > since it depends so much on particular details of kernel memory usage. I agree. > Given the results of these experiments I'm tempted to remove the 2% > minimum that is already in the tree -- vendors can make their own patch > if they have a better idea of what works for their particular kernel > setups. I second this opinion. I think it is better if you remove the 2% minimum. It really serves no purpose in the majority of situations. Aravindh _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |