| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] linux balloon question |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | 2008年12月19日 14:21:08 +0000 |
| Delivery-date: | 2008年12月19日 06:21:09 -0800 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
What is the point of having separate bs.current_pages and totalram_pages? The latter (in current code) always tracks the former. Further, what's the point of re-initializing totalram_pages during balloon_init() in pv guests? If the bogus incrementing of the value in mem_init() gets removed, things would match native without that re-initialization, and the current_pages member could entirely go away. Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] GPLPV drivers 0.9.12-pre9 upload , Jun Koi |
|---|---|
| Next by Date: | Re: [Xen-devel] GPLPV drivers 0.9.12-pre9 upload , Ian Jackson |
| Previous by Thread: | [Xen-devel] GPLPV drivers 0.9.12-pre9 upload , James Harper |
| Next by Thread: | [Xen-devel] Fourth release candidates for 3.2.3 and 3.3.1 , Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |