All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>,
	"Nick Couchman" <Nick.Couchman@seakr.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Mr. Teo En Ming (Zhang Enming)" <space.time.universe@gmail.com>,
	"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>,
	Robert Dunkley <Robert@saq.co.uk>
Subject: Re: [Xen-devel] Re: Max. PV and HVM Guests
Date: Mon, 09 Nov 2009 15:24:59 +0000	[thread overview]
Message-ID: <C71DE4CB.199C4%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20091109151750.GN16033@reaktio.net>

On 09/11/2009 15:17, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:

>> Furthermore, while I'm not
>> Linux developer and so not familiar with how Linux calculates buffering
>> and caching, I do know that my Linux systems dynamically manage buffers
>> and caches, and when memory is reduced or some application requires a
>> larger amount of physical memory, Linux reduces the amount of data in
>> buffers and caches.
>> 
> 
> Yeah, it has to do with sizing the network buffers, caches etc..
> 
> It shouldn't _crash_, so Teo is seeing some bug I believe. But it has
> always been "best practice" to limit dom0 memory - and prevent weird
> things happening later (like "memory squeeze in netback driver").

The issue is not really kernel data like network buffers and buffer cache.
It is kernel memory metadata -- primarily the per-page info structure that
the kernel maintains. The metadata doesn't get shrunk with memory size when
ballooning out, hence it increases as a proportion of memory still assigned
to the domain. That really is significant when aggressively ballooning down
a large-memory domain.

 -- Keir

  reply	other threads:[~2009-11-09 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 15:06 Re: [Xen-users] Max. PV and HVM Guests Nick Couchman
2009-11-09 15:17 ` [Xen-devel] " Pasi Kärkkäinen
2009-11-09 15:24   ` Keir Fraser [this message]
2009-11-09 15:27     ` Re: [Xen-users] " Pasi Kärkkäinen
2009-11-09 15:39   ` Dan Magenheimer
2009-11-09 15:18 ` [Xen-devel] " Keir Fraser
2009-11-09 15:29   ` Re: [Xen-users] " Nick Couchman
2009-11-09 15:41     ` [Xen-devel] " Mr. Teo En Ming (Zhang Enming)
  -- strict thread matches above, loose matches on Subject: below --
2009-11-08 11:45 Mr. Teo En Ming (Zhang Enming)
2009-11-08 13:01 ` Moi meme
2009-11-09  8:17   ` [Xen-users] " Robert Dunkley
2009-11-09 10:52     ` Mr. Teo En Ming (Zhang Enming)
2009-11-09 11:54       ` [Xen-devel] " Pasi Kärkkäinen
2009-11-09 12:01         ` Re: [Xen-users] " Mr. Teo En Ming (Zhang Enming)
2009-11-09 12:05           ` Pasi Kärkkäinen
2009-11-09 12:14             ` Mr. Teo En Ming (Zhang Enming)
2009-11-09 12:18               ` Pasi Kärkkäinen
2009-11-09 13:10                 ` Mr. Teo En Ming (Zhang Enming)
2009-11-09 14:37                   ` [Xen-devel] " Mr. Teo En Ming (Zhang Enming)

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=C71DE4CB.199C4%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Nick.Couchman@seakr.com \
    --cc=Robert@saq.co.uk \
    --cc=pasik@iki.fi \
    --cc=space.time.universe@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.