All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Johansson" <esj@harvee.org>
To: xen-devel@lists.sourceforge.net
Subject: memory allocation guidance
Date: Fri, 04 Mar 2005 15:50:43 -0500	[thread overview]
Message-ID: <4228CA23.1040406@harvee.org> (raw)

I've been reading to the documentation and I'm not really clear on how 
to allocate memory.  The impression that gathered is that the allocation 
specification is the initial allocation given to a domain.  From there 
additional memory can be allocated/deallocated to a domain courtesy to 
balloon driver/handler.

I would appreciate a pointer to some documentation or some guidance in 
deciding how to allocate memory to a domain and how it will behave as 
the system runs.  No need for any deep system level information.  I'm 
really looking for operational guidelines and enough background to 
understand why the choices are made.

part of what triggers this request is that my xen server was acting 
funny (i.e. significant lags in processing, lots of paging) and I 
discovered a bad memory stick.  Much joy.  ;-)

---eric

-- 
http://www.wired.com/wired/archive/13.03/view.html?pg=5

The result of the duopoly that currently defines "competition" is that
prices and service suck. We're the world's leader in Internet
technology - except that we're not.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

                 reply	other threads:[~2005-03-04 20:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4228CA23.1040406@harvee.org \
    --to=esj@harvee.org \
    --cc=xen-devel@lists.sourceforge.net \
    /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.