From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Dmitry Fleytman" <dmitry.fleytman@gmail.com>,
qemu-trivial@nongnu.org, "Jason Wang" <jasowang@redhat.com>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"Greg Kurz" <groug@kaod.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH 0/3] hw/net,virtfs-proxy-helper: Reduce .data footprint
Date: Thu, 5 Mar 2020 02:04:43 +0100 [thread overview]
Message-ID: <20200305010446.17029-1-philmd@redhat.com> (raw)
More memory footprint reduction, similar to:
https://lists.gnu.org/archive/html/qemu-devel/2020-03/msg00984.html
The elf-dissector tool [1] [2] helped to notice the big array.
[1] https://phabricator.kde.org/source/elf-dissector/
[2] https://www.volkerkrause.eu/2019/06/22/elf-dissector-aarch64-support.html
Philippe Mathieu-Daudé (3):
hw/net/e1000: Add readops/writeops typedefs
hw/net/e1000: Move macreg[] arrays to .rodata to save 1MiB of .data
virtfs-proxy-helper: Make the helper_opts[] array const
fsdev/virtfs-proxy-helper.c | 2 +-
hw/net/e1000.c | 6 ++++--
hw/net/e1000e_core.c | 6 ++++--
3 files changed, 9 insertions(+), 5 deletions(-)
--
2.21.1
next reply other threads:[~2020-03-05 1:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 1:04 Philippe Mathieu-Daudé [this message]
2020-03-05 1:04 ` [PATCH 1/3] hw/net/e1000: Add readops/writeops typedefs Philippe Mathieu-Daudé
2020-03-05 9:16 ` Dmitry Fleytman
2020-03-05 1:04 ` [PATCH 2/3] hw/net/e1000: Move macreg[] arrays to .rodata to save 1MiB of .data Philippe Mathieu-Daudé
2020-03-05 9:16 ` Dmitry Fleytman
2020-03-05 1:04 ` [PATCH 3/3] virtfs-proxy-helper: Make the helper_opts[] array const Philippe Mathieu-Daudé
2020-03-05 10:10 ` Greg Kurz
2020-03-05 9:53 ` [PATCH 0/3] hw/net,virtfs-proxy-helper: Reduce .data footprint Stefano Garzarella
2020-03-05 10:37 ` Philippe Mathieu-Daudé
2020-03-05 10:41 ` Stefano Garzarella
2020-03-06 9:25 ` Paolo Bonzini
2020-03-09 11:44 ` Laurent Vivier
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=20200305010446.17029-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=dmitry.fleytman@gmail.com \
--cc=groug@kaod.org \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=qemu_oss@crudebyte.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).