All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Ky Srinivasan <ksrinivasan@novell.com>
Cc: xen-devel@lists.xensource.com,
	Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com>
Subject: Re: [PATCH] Make "xm mem-set" be lowerboundondomX-min-mem
Date: Mon, 22 May 2006 10:35:05 -0700	[thread overview]
Message-ID: <4471F649.70203@us.ibm.com> (raw)
In-Reply-To: <4471BC98.E57C.0030.0@novell.com>

Ky Srinivasan wrote:
>>>>On Mon, May 22, 2006 at  1:01 pm, in message
> 
> <4a7c24c6870aa1e8619e99a32a90c8c6@cl.cam.ac.uk>, Keir Fraser
> <Keir.Fraser@cl.cam.ac.uk> wrote: 
> 
> 
>>On 22 May 2006, at 17:54, Ky Srinivasan wrote:
>>
>>
>>>Kier,
>>>
>>>The  floor was chosen because we found the system to be unreliable
>>>below that value (in the tests we did on sles 10). A floor I think
> 
> is
> 
>>>useful to have even if the value picked is a different one.
>>
>>192MB is on the high side isn't it?
> 
> 
> We have a  couple of bugs in our bugzilla where dom0 could not be
> booted with memory set to 128 MB. I don't know what the right floor is,
> but it has to be more than 128M.

Under what circumstances was that the case, do you
know? It doesn't seem like the normal default case,
we've certainly not run into that one...

thanks,
Nivedita

  reply	other threads:[~2006-05-22 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22 16:31 [PATCH] Make "xm mem-set" be lowerboundondomX-min-mem Puthiyaparambil, Aravindh
2006-05-22 16:34 ` Keir Fraser
2006-05-22 16:54   ` Ky Srinivasan
2006-05-22 17:01     ` Keir Fraser
2006-05-22 17:28       ` Ky Srinivasan
2006-05-22 17:35         ` Nivedita Singhvi [this message]
2006-05-22 19:25         ` Ky Srinivasan
2006-05-23  7:18           ` 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=4471F649.70203@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=aravindh.puthiyaparambil@unisys.com \
    --cc=ksrinivasan@novell.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.