From: Erik Hensema <erik@hensema.net>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Xen-users] (xen) Possible bug: Memory squeeze in netback driver.
Date: Wed, 7 Jun 2006 17:52:26 +0200 [thread overview]
Message-ID: <200606071752.26963.erik@hensema.net> (raw)
In-Reply-To: <4485F70E.4020602@us.ibm.com>
On Tuesday 06 June 2006 23:43, Anthony Liguori wrote:
> This is a rather curious path in the code involving rate limiting
> that I'm not all that familiar with. Does it help is you create
> the domains with a large maxmem than memory? For instance:
>
> maxmem = 512
> memory = 256
Yes, it does seem to help. I've recreated almost all domains with 16
MB 'headroom', now I can create domains up until the point I run out
of loop devices ;-) (6 domU's running ATM)
I'll reboot tonight (or shutdown all domains and reload the loop
module) and try to start more domains.
--
Erik Hensema (erik@hensema.net)
next prev parent reply other threads:[~2006-06-07 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606062047.44746.erik@hensema.net>
2006-06-06 21:43 ` [Xen-users] (xen) Possible bug: Memory squeeze in netback driver Anthony Liguori
2006-06-07 15:52 ` Erik Hensema [this message]
2006-06-07 20:43 ` Anthony Liguori
2006-06-08 7:30 ` 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=200606071752.26963.erik@hensema.net \
--to=erik@hensema.net \
--cc=aliguori@us.ibm.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.