From: Kip Macy <kmacy@fsmware.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: suspending a domain in the ngio world
Date: Sat, 15 May 2004 11:10:02 -0700 (PDT) [thread overview]
Message-ID: <20040515105343.V86487@demos.bsdclusters.com> (raw)
In-Reply-To: <E1BP3Bv-0006zQ-00@mta1.cl.cam.ac.uk>
The dd is running in DOM1. The OOM killer is getting run in DOM0.
There is clearly a memory leak in the block I/O path.
DOM0 is curly and DOM1 is xen-vm0.
A large amount of memory has already been leaked:
kmacy@curly cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 262565888 205619200 56946688 0 23339008 28123136
==
[root@xen-vm0 ~]$ dd if=/dev/zero of=/tmp/bwout bs=1024k count=256
==
kmacy@curly cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 262565888 214687744 47878144 0 23339008 28123136
==
[root@xen-vm0 ~]$ dd if=/dev/zero of=/tmp/bwout count=256 bs=1024k
256+0 records in
256+0 records out
==
kmacy@curly cat /proc/meminfo | head -3
total: used: free: shared: buffers: cached:
Mem: 262565888 223727616 38838272 0 23339008 28123136
==
[root@xen-vm0 ~]$ dd if=/dev/zero of=/tmp/bwout count=256 bs=1024k
256+0 records in
256+0 records out
==
kmacy@curly cat /proc/meminfo | head -2
total: used: free: shared: buffers: cached:
Mem: 262565888 232873984 29691904 0 23339008 28123136
So ~40MB is leaked for every 1GB transferred.
I can give you a stack backtrace of the memory allocation failure in
DOM0 if you like, but as far as I can tell the horse has long since left
the barn at that point.
> This is within DOM1 (i.e., not DOM0) right? If so, I guess that doing
> this 'dd' test within DOM0 doesn't get you similar messages?
>
> This is rather unexpected -- if you could add a stack backtrace to the
> out-of-memory path in the page allocator (page_alloc.c in Xenolinux)
> an d post me that with the kernel image (vmlinux) then I'll see what I
> can work out. I guess I haven't tested all that hard so there might be
> a memory leak.
On a side note - I don't need suspend/restore, I just need coredump and
almost immediately after that PTRACE_STOP. So long as I can stop the
domain long enough to write out its state I have what I need.
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-15 18:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040513221648.W77678@demos.bsdclusters.com>
2004-05-14 6:35 ` system lockup when starting secondary domains Keir Fraser
2004-05-14 20:56 ` Kip Macy
2004-05-14 21:02 ` never mind was " Kip Macy
2004-05-14 21:25 ` telnet xend Kip Macy
2004-05-14 21:33 ` Ian Pratt
2004-05-14 21:48 ` Kip Macy
2004-05-14 22:37 ` Kip Macy
2004-05-14 22:39 ` Kip Macy
2004-05-14 22:49 ` Ian Pratt
2004-05-14 23:14 ` Kip Macy
2004-05-15 4:26 ` suspending a domain in the ngio world Kip Macy
2004-05-15 5:17 ` Kip Macy
2004-05-15 8:16 ` Keir Fraser
2004-05-15 15:51 ` Kip Macy
2004-05-15 16:12 ` Keir Fraser
2004-05-15 17:02 ` Kip Macy
2004-05-15 17:43 ` Keir Fraser
2004-05-15 18:10 ` Kip Macy [this message]
2004-05-15 23:21 ` 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=20040515105343.V86487@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.