All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Jan Beulich <jbeulich@novell.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: Re: Xenheap disappearance: (was: xen_phys_startfor32b)
Date: Mon, 19 Jan 2009 20:04:00 +0000 (GMT)	[thread overview]
Message-ID: <7053cd45-cb7e-4e80-a46a-c2ad7d33ff4f@default> (raw)
In-Reply-To: <49744659.76E4.0078.0@novell.com>

> as I frequently see systems with completely empty domain heaps.

Really?  Oh, I see we probably have different default paradigms
for memory allocation.  On Oracle VM, dom0 is by default
launched with 256MB and all remaining memory is "free" and
guests are generally launched with memory==maxmem.  As a
result, it is very unusual to have an empty domheap due
to fragmentation.

I expect you are running without dom0_mem unset, thus
using auto-ballooning from dom0 by default.  And probably
either guests are usually launched with memory<<maxmem or
are using disk='file:...' (which results in dom0 filling
up its page cache) or both.  True?

> *must* be accompanied by a tools change in order to be usable

Yes, I see that it would be a must for your different paradigm,
but less important in the one I am accustomed to.

Thanks,
Dan

> >>> Dan Magenheimer <dan.magenheimer@oracle.com> 17.01.09 00:16 >>>
> >I'm not sure what you are getting at.  Are you saying that
> >creating a domain takes (big)MB from domheap, then later
> >(little)KB from xenheap, and if we combine domheap and xenheap,
> >the tools might launch a domain when available memory is
> >greater than (big)MB but smaller than (big)MB+(small)KB,
> >and that will result in the tools thinking the domain
> >can launch but it won't?  I suppose that's possible,
> 
> Yes, that's what I'm trying to say. And I think it's rather 
> likely to happen,
> as I frequently see systems with completely empty domain heaps.
> 
> >but exceedingly unlikely.  And I think Keir's plan will
> >have the same problem.  Sounds like a tools bug, not a
> >reason to avoid modernizing Xen memory management.
> 
> No, I wasn't making the point to ask for not doing 
> improvements in Xen -
> in fact, it's been for a long time that I've been raising the 
> scalability issue
> of the limited Xen heap. I was just trying to point out that 
> the Xen change
> *must* be accompanied by a tools change in order to be usable in other
> than development/test environments.
> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2009-01-19 20:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06  6:36 xen_phys_start for 32b Cihula, Joseph
2009-01-06  8:42 ` Keir Fraser
2009-01-06 18:29   ` Cihula, Joseph
2009-01-06 22:12     ` Keir Fraser
2009-01-06 22:19       ` Cihula, Joseph
2009-01-07  8:54         ` Keir Fraser
2009-01-07 15:13           ` Cihula, Joseph
2009-01-07 15:40             ` Keir Fraser
2009-01-07 21:37               ` Cihula, Joseph
2009-01-07 23:27                 ` Keir Fraser
2009-01-08  0:17               ` Xenheap disappearance: (was: xen_phys_start for 32b) Dan Magenheimer
2009-01-08  9:04                 ` Keir Fraser
2009-01-08 17:53                   ` Dan Magenheimer
2009-01-14 22:45                   ` Dan Magenheimer
2009-01-15  0:27                     ` Dan Magenheimer
2009-01-15  1:48                       ` Dan Magenheimer
2009-01-15  8:38                     ` Keir Fraser
2009-01-15  8:41                       ` Keir Fraser
2009-01-15 18:15                       ` Dan Magenheimer
2009-01-15 18:51                         ` Keir Fraser
2009-01-16  8:11                           ` Re: Xenheap disappearance: (was: xen_phys_start for32b) Jan Beulich
2009-01-16 23:16                             ` Dan Magenheimer
2009-01-19  8:22                               ` Re: Xenheap disappearance: (was: xen_phys_startfor32b) Jan Beulich
2009-01-19 20:04                                 ` Dan Magenheimer [this message]
2009-01-20  9:11                                   ` Re: Xenheap disappearance: (was:xen_phys_startfor32b) Jan Beulich
2009-01-20  9:16                                     ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7053cd45-cb7e-4e80-a46a-c2ad7d33ff4f@default \
    --to=dan.magenheimer@oracle.com \
    --cc=jbeulich@novell.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.