From: Olaf Hering <olaf@aepfle.de>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: memory leak in block/xen_disk in qemu-3.x
Date: Tue, 11 Dec 2018 17:07:52 +0100 [thread overview]
Message-ID: <20181211160752.GD18447@aepfle.de> (raw)
In-Reply-To: <74c1c30c147444cea915ee1befa56cf6@AMSPEX02CL03.citrite.net>
[-- Attachment #1.1: Type: text/plain, Size: 785 bytes --]
On Tue, Dec 11, Paul Durrant wrote:
> > -----Original Message-----
> > From: Xen-devel [mailto:xen-devel-bounces@lists.xenproject.org] On Behalf
> > Of Olaf Hering
> > Sent: 11 December 2018 15:31
> > To: xen-devel@lists.xenproject.org; qemu-devel@nongnu.org
> > Subject: [Xen-devel] memory leak in block/xen_disk in qemu-3.x
> >
> > What are the live time rules of ioreq->buf?
> > In my testing the memory usage of qemu is constantly growing from about
> > 250MB to several GB after a few days.
> Are you perhaps running into the problem addressed by this patch?
> https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg00244.html
This looks like a fix, rather than an improvement.
More than a month passed already, why is it not yet in qemu.git#master?
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Olaf Hering <olaf@aepfle.de>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Xen-devel] memory leak in block/xen_disk in qemu-3.x
Date: Tue, 11 Dec 2018 17:07:52 +0100 [thread overview]
Message-ID: <20181211160752.GD18447@aepfle.de> (raw)
In-Reply-To: <74c1c30c147444cea915ee1befa56cf6@AMSPEX02CL03.citrite.net>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Tue, Dec 11, Paul Durrant wrote:
> > -----Original Message-----
> > From: Xen-devel [mailto:xen-devel-bounces@lists.xenproject.org] On Behalf
> > Of Olaf Hering
> > Sent: 11 December 2018 15:31
> > To: xen-devel@lists.xenproject.org; qemu-devel@nongnu.org
> > Subject: [Xen-devel] memory leak in block/xen_disk in qemu-3.x
> >
> > What are the live time rules of ioreq->buf?
> > In my testing the memory usage of qemu is constantly growing from about
> > 250MB to several GB after a few days.
> Are you perhaps running into the problem addressed by this patch?
> https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg00244.html
This looks like a fix, rather than an improvement.
More than a month passed already, why is it not yet in qemu.git#master?
Olaf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2018-12-11 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 15:30 memory leak in block/xen_disk in qemu-3.x Olaf Hering
2018-12-11 15:30 ` [Qemu-devel] " Olaf Hering
2018-12-11 16:01 ` Paul Durrant
2018-12-11 16:01 ` [Qemu-devel] [Xen-devel] " Paul Durrant
2018-12-11 16:07 ` Olaf Hering [this message]
2018-12-11 16:07 ` Olaf Hering
2018-12-11 16:15 ` Paul Durrant
2018-12-11 16:15 ` [Qemu-devel] [Xen-devel] " Paul Durrant
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=20181211160752.GD18447@aepfle.de \
--to=olaf@aepfle.de \
--cc=Paul.Durrant@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xenproject.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 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.