From: Olivier Bonvalet <xen.list@daevel.fr>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-users@lists.xen.org, Roger Pau Monne <roger.pau@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [Xen-users] unexpected Out Of Memory (OOM)
Date: Thu, 08 Aug 2013 12:10:17 +0200 [thread overview]
Message-ID: <1375956617.13572.51.camel@localhost> (raw)
In-Reply-To: <1375952296.619.83.camel@kazak.uk.xensource.com>
Le jeudi 08 août 2013 à 09:58 +0100, Ian Campbell a écrit :
> On Wed, 2013-08-07 at 23:37 +0200, Olivier Bonvalet wrote:
> > So I recompiled a kernel with the kmemleak feature. I obtain that kind
> > of list, but not sure that it's usefull :
>
> These look to me like valid things to be allocating at boot time, and
> even if they are leaked there isn't enough here to exhaust 8GB by a long
> way.
>
> It'd be worth monitoring to see if it grows at all or if anything
> interesting shows up after running for a while with the leak.
>
> Likewise it'd be worth keeping an eye on the process list and slabtop
> and seeing if anything appears to be growing without bound.
>
> Other than that I'm afraid I don't have many smart ideas.
>
> Ian.
>
>
Ok, then I will become crazy : when I start the kernel with kmemleak=on
in fact I haven't memory leak. The memory usage stay near 300MB.
Then I restart on the same kernel, without kmemleak=on, the memory usage
jump to 600MB and still grow.
Olivier
PS : I retry several time, to confirm that.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-08 10:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 0:02 unexpected Out Of Memory (OOM) Olivier Bonvalet
2013-08-07 8:29 ` [Xen-users] " Ian Campbell
2013-08-07 8:58 ` Olivier Bonvalet
2013-08-07 9:35 ` Olivier Bonvalet
2013-08-07 9:46 ` Olivier Bonvalet
2013-08-07 10:16 ` Ian Campbell
2013-08-07 11:17 ` Olivier Bonvalet
2013-08-07 13:36 ` Ian Campbell
2013-08-07 14:26 ` Olivier Bonvalet
2013-08-07 21:37 ` Olivier Bonvalet
2013-08-08 8:58 ` Ian Campbell
2013-08-08 10:10 ` Olivier Bonvalet [this message]
2013-08-08 10:18 ` Ian Campbell
2013-08-08 11:43 ` Olivier Bonvalet
2013-08-08 13:25 ` Wei Liu
2013-08-08 14:17 ` Olivier Bonvalet
2013-08-09 12:53 ` Konrad Rzeszutek Wilk
2013-08-07 14:48 ` Wei Liu
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=1375956617.13572.51.camel@localhost \
--to=xen.list@daevel.fr \
--cc=Ian.Campbell@citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xen.org \
/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).