From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: jcody@redhat.com, qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH v2 0/2] sheepdog: remove huge BSS object
Date: Wed, 23 May 2018 18:07:19 +0200 [thread overview]
Message-ID: <20180523160721.14018-1-pbonzini@redhat.com> (raw)
block/sheepdog.o has a 4M static variable that is 90% of QEMU's whole .bss
section. Since it doesn't really have to be static, we can just use a
heap allocated block. We can actually make it smaller too. :)
Patch 1 is a related cleanup since we're touching that area of the code.
Paolo
v1->v2: free the data...
Paolo Bonzini (2):
sheepdog: cleanup repeated expression
sheepdog: remove huge BSS object
block/sheepdog.c | 27 ++++++++++++++-------------
1 file changed, 14 insertions(+), 13 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-23 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 16:07 Paolo Bonzini [this message]
2018-05-23 16:07 ` [Qemu-devel] [PATCH 1/2] sheepdog: cleanup repeated expression Paolo Bonzini
2018-05-23 16:07 ` [Qemu-devel] [PATCH 2/2] sheepdog: remove huge BSS object Paolo Bonzini
2018-05-23 16:19 ` [Qemu-devel] [PATCH v2 0/2] " Jeff Cody
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=20180523160721.14018-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jcody@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).