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 16:18:53 +0000 [thread overview]
Message-ID: <4B7D767D0200007800030229@vpn.id2.novell.com> (raw)
In-Reply-To: <b5a8d8a9-e991-4118-9783-8be1f29fef52@default>
>>> Dan Magenheimer <dan.magenheimer@oracle.com> 18.02.10 17:09 >>>
>But ignoring my flimsy excuses, Jan, do you have some debug code
>you are using to identify order>0 allocations? If so, could I
>have a copy... and perhaps Keir would consider adding
>it post-4.0 to make it easier to search-and-destroy.
I actually noticed this only as a side effect from a much uglier debugging
patch - observing apparent memory corruption with no apparent pattern
during save/restore/migrate, I finally decided to try a brute force method
and track all allocations. Since you are so eager to point out and fix all
order > 0 allocations, I was quite surprised to see one while tmem
itself initialized its state for Dom0. Hence I thought I'd point it out. The
patch as it stands is, I think, not really a general debugging aid - if you
think differently, I can of course still share it.
Jan
next prev parent reply other threads:[~2010-02-18 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 8:04 Memory fragmentation, order>0 allocation, and 4.0 dynamic RAM optimization features Jan Beulich
2010-02-18 16:09 ` Dan Magenheimer
2010-02-18 16:18 ` Jan Beulich [this message]
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=4B7D767D0200007800030229@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).