[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Balloon driver and oom-killer
- To: xen-devel@xxxxxxxxxxxxxxxxxxx
- From: "ashutosh mehra" <ashutosh.xen@xxxxxxxxx>
- Date: Fri, 26 Oct 2007 23:51:28 +0530
- Delivery-date: Fri, 26 Oct 2007 11:22:08 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=aNoYdP9IP29F4ovZuwE4N28jilHDCLb3EpsjzenlqUweFc9s7qwJsKapI1BsKkNYSsV+WZW6pS/rEHxM9tns7OKjcKyS6mauIUFnE8QJn0CSgOHFtNStVKwH8RXi7oGGk5pbII0B0jgi2plyu1/Ra3vPPDpmCM/YC3trOXeo0K4=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Hi,
I'm working on the following topic from the xen roadmap as a part of an academic project: "Improve interaction between balloon driver and page allocator to avoid memory crunch."
I have a few doubts regarding what exactly needs to be done:
- Should the working of the balloon driver be same as in the case of VMware ESX balloon driver? ( http://www.vmware.com/pdf/usenix_resource_mgmt.pdf
)
- Should the balloon driver be made capable of inflating/deflating the balloon automatically or only manually by using xm mem-set?
- The guest OS balloon driver will have to be modified, will any modifications to xen(dom0) be required?
- What exactly does the number of pages in high- and low-memory balloons in the balloon_stats structure and in the output of cat /proc/xen/balloon mean?
- What is the current state of the balloon driver?
Please correct me if my any of my assumptions are wrong. I'd be very grateful if someone could provide any information regarding this.
Thanks,
Ashutosh
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
