From: "Jan Beulich" <JBeulich@novell.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: xen-devel@lists.xensource.com, Tim Deegan <Tim.Deegan@citrix.com>,
GeorgeDunlap <george.dunlap@eu.citrix.com>,
PatrickColp <pjcolp@cs.ubc.ca>,
Ian Pratt <Ian.Pratt@eu.citrix.com>,
Andrew Peace <Andrew.Peace@eu.citrix.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Grzegorz Milos <gm281@cam.ac.uk>
Subject: Re: Memory fragmentation, order>0 allocation, and 4.0 dynamic RAM optimization features
Date: Thu, 18 Feb 2010 08:04:51 +0000 [thread overview]
Message-ID: <4B7D02B302000078000300BF@vpn.id2.novell.com> (raw)
>>> Dan Magenheimer <dan.magenheimer@oracle.com> 08.02.10 19:13 >>>
>Are there other known order>0 allocations that might result
>in similar issues?
Interestingly, tmem itself indirectly causes order-1 allocations (through
the use of xmem_pool_create(), sizeof(struct xmem_pool) = 0x18d0
on a non-debug build).
Jan
next reply other threads:[~2010-02-18 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 8:04 Jan Beulich [this message]
2010-02-18 16:09 ` Memory fragmentation, order>0 allocation, and 4.0 dynamic RAM optimization features Dan Magenheimer
2010-02-18 16:18 ` Jan Beulich
2010-02-18 17:32 ` Dan Magenheimer
2010-02-18 20:46 ` xe pool_reject support on XCP Chonduy Nguyen
2010-02-18 23:54 ` Dave Scott
2010-02-19 0:36 ` XCP event tracking Chonduy Nguyen
2010-02-19 1:34 ` XCP: Real-time Performance Monitoring and Alerting Chonduy Nguyen
-- strict thread matches above, loose matches on Subject: below --
2010-02-08 18:13 Memory fragmentation, order>0 allocation, and 4.0 dynamic RAM optimization features Dan Magenheimer
2010-02-08 19:11 ` Keir Fraser
2010-02-09 10:50 ` Tim Deegan
2010-02-09 13:13 ` Jan Beulich
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=4B7D02B302000078000300BF@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Andrew.Peace@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=george.dunlap@eu.citrix.com \
--cc=gm281@cam.ac.uk \
--cc=keir.fraser@eu.citrix.com \
--cc=pjcolp@cs.ubc.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).