qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Yang Zhong <yang.zhong@intel.com>
Cc: qemu-devel@nongnu.org, berrange@redhat.com, pbonzini@redhat.com,
	stone.xulei@huawei.com, arei.gonglei@huawei.com,
	wangxinxin.wang@huawei.com, weidong.huang@huawei.com,
	zhang.zhanghailiang@huawei.com, liujunjie23@huawei.com
Subject: Re: [Qemu-devel] [PATCH v3] rcu: reduce more than 7MB heap memory by malloc_trim()
Date: Fri, 24 Nov 2017 11:27:01 +0000	[thread overview]
Message-ID: <20171124112701.GB11868@stefanha-x1.localdomain> (raw)
In-Reply-To: <1511505030-3669-1-git-send-email-yang.zhong@intel.com>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

On Fri, Nov 24, 2017 at 02:30:30PM +0800, Yang Zhong wrote:
> diff --git a/configure b/configure
> index 0c6e757..6292ab0 100755
> --- a/configure
> +++ b/configure
> @@ -426,6 +426,7 @@ vxhs=""
>  supported_cpu="no"
>  supported_os="no"
>  bogus_os="no"
> +malloc_trim="yes"

Looks pretty good, sorry I forgot to mention two things:

Please add the --enable-malloc-trim/--disable-malloc-trim options so
it's easy to build QEMU with or without this feature.  For example, if
someone is debugging a performance issue they may wish to rebuild with
--disable-malloc-trim to confirm that trimming hasn't caused a
regression.

Also please change this line to malloc_trim="" so the "Disabling
malloc_trim with non-libc memory allocator" error message is only
printed when --enable-malloc-trim was explicitly given by the user.
Otherwise the message is always printed when QEMU is built with
jemalloc/tcmalloc - that's too noisy.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2017-11-24 11:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24  6:30 [Qemu-devel] [PATCH v3] rcu: reduce more than 7MB heap memory by malloc_trim() Yang Zhong
2017-11-24 11:27 ` Stefan Hajnoczi [this message]
2017-11-26  6:17 ` Shannon Zhao
2017-11-27  3:06   ` Zhong Yang
2017-11-27 11:59     ` Paolo Bonzini
     [not found]   ` <20171201105622.GB26237@yangzhon-Virtual>
     [not found]     ` <74cccd14-e485-90d4-82d9-03355c05faca@redhat.com>
2017-12-04 12:03       ` Yang Zhong
2017-12-04 12:07         ` Daniel P. Berrange
2017-12-04 12:16           ` Yang Zhong
2017-12-04 12:18           ` Paolo Bonzini
2017-12-04 12:26         ` Shannon Zhao
2017-12-05  6:00           ` Yang Zhong
2017-12-05 14:10             ` Paolo Bonzini
2017-12-06  9:26               ` Yang Zhong
2017-12-06  9:48                 ` Paolo Bonzini
2017-12-07 15:06                   ` Yang Zhong
2017-12-11 16:31                     ` Paolo Bonzini
2017-12-12  6:54                       ` Yang Zhong
2017-12-12  7:09                         ` Shannon Zhao
2017-12-18  7:17                         ` Shannon Zhao
2017-12-18  7:51                           ` Yang Zhong
2017-12-19 12:57                             ` Paolo Bonzini
2017-12-08 11:06                   ` Yang Zhong

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=20171124112701.GB11868@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=berrange@redhat.com \
    --cc=liujunjie23@huawei.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stone.xulei@huawei.com \
    --cc=wangxinxin.wang@huawei.com \
    --cc=weidong.huang@huawei.com \
    --cc=yang.zhong@intel.com \
    --cc=zhang.zhanghailiang@huawei.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).