All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Kemp <steve@bytemark.co.uk>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: How to diagnose memory leak in kvm-qemu-0.14.0?
Date: Fri, 20 May 2011 15:52:46 +0100	[thread overview]
Message-ID: <20110520145246.GN27422@bytemark.co.uk> (raw)
In-Reply-To: <BANLkTinZoJmP3uNw9L1-Be82Xy-A3gXeMg@mail.gmail.com>

On Fri May 20, 2011 at 15:32:34 +0100, Stefan Hajnoczi wrote:

> >  virtio_blk_alloc_request 0.000 req=0x91e08f0  -> Allocation 1
> >  virtio_blk_alloc_request 77.659 req=0x9215650  -> Allocation 2
>
> Are you sure this isn't the temporary one that is allocated but freed
> immediately once the virtqueue is empty:

  Good catch.  Adding traces above both the qemu_free() calls I can
 see that the allocation & freeing of VirtIOBlockReq structures
 is paired.

  Looks like I'm going to have to bite the bullet and do real allocation
 tracking.

Steve Kemp
--
                                          Bytemark Hosting
                                http://www.bytemark.co.uk/
                                  phone UK: 0845 004 3 004
          Dedicated Linux hosts from 15ukp ($30) per month

      reply	other threads:[~2011-05-20 14:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 16:44 How to diagnose memory leak in kvm-qemu-0.14.0? Steve Kemp
2011-05-19  8:40 ` Stefan Hajnoczi
2011-05-19  8:50   ` Stefan Hajnoczi
2011-05-19 11:00   ` Steve Kemp
2011-05-19 11:57   ` Steve Kemp
2011-05-20 11:01     ` Stefan Hajnoczi
2011-05-20 11:47       ` Steve Kemp
2011-05-20 13:16         ` Stefan Hajnoczi
2011-05-20 13:47           ` Steve Kemp
2011-05-20 14:32             ` Stefan Hajnoczi
2011-05-20 14:52               ` Steve Kemp [this message]

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=20110520145246.GN27422@bytemark.co.uk \
    --to=steve@bytemark.co.uk \
    --cc=kvm@vger.kernel.org \
    --cc=stefanha@gmail.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.