From: Julien Grall <julien@xen.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v4 3/3] unzstd: make helper symbols static
Date: Wed, 5 May 2021 18:35:04 +0100 [thread overview]
Message-ID: <f6e00fd9-a207-858e-37e8-fb25427cf8de@xen.org> (raw)
In-Reply-To: <1696e5f2-481a-5a7f-258d-b2a0679b041f@suse.com>
On 29/04/2021 14:26, Jan Beulich wrote:
> On 29.04.2021 13:27, Julien Grall wrote:
>> On 21/04/2021 11:22, Jan Beulich wrote:
>>> While for the original library's purposes these functions of course want
>>> to be externally exposed, we don't need this, and we also don't want
>>> this both to prevent unintended use and to keep the name space tidy.
>>> (When functions have no callers at all, wrap them with a suitable
>>> #ifdef.) This has the added benefit of reducing the resulting binary
>>> size - while this is all .init code, it's still desirable to not carry
>>> dead code.
>>
>> So I understand the desire to keep the code close to Linux and removing
>> the dead code. However I am still not convinced that the approach taken
>> is actually worth the amount of memory saved.
>>
>> How much memory are we talking about here?
>
> There are no (runtime) memory savings, as is being said by the
> description. There are savings on the image and symbol table sizes
> (see below - .*.0/ holding files as produced without the patch
> applied, while .*.1/ holding output with it in place), the image
> size reduction part of which is - as also expressed by the
> description - a nice side effect, but not the main motivation for
> the change.
Thanks for the providing the information. I have misunderstood your
original intention.
Reading them again, I have to admit this doesn't really change my view
here. You are trading a smaller name space or prevent unintended use
(not clear what would be wrong to call them) to code
maintenability/readability.
At the same time, this is not a code I usually work on (even if I am
meant to maintain it). I will leave another maintainer to make the
decision here.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2021-05-05 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 10:20 [PATCH v4 0/3] zstd decompression fallout / consolidation Jan Beulich
2021-04-21 10:21 ` [PATCH v4 1/3] unzstd: replace INIT and STATIC Jan Beulich
2021-04-29 11:05 ` Julien Grall
2021-04-21 10:21 ` [PATCH v4 2/3] xen/decompress: drop STATIC and INIT Jan Beulich
2021-04-21 10:22 ` [PATCH v4 3/3] unzstd: make helper symbols static Jan Beulich
2021-04-29 11:27 ` Julien Grall
2021-04-29 13:26 ` Jan Beulich
2021-05-05 17:35 ` Julien Grall [this message]
2021-05-06 6:21 ` Jan Beulich
2021-05-06 12:54 ` Julien Grall
2021-06-30 7:43 ` Ping: " Jan Beulich
2021-11-04 9:45 ` Jan Beulich
2021-04-29 9:19 ` Ping: [PATCH v4 0/3] zstd decompression fallout / consolidation Jan Beulich
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=f6e00fd9-a207-858e-37e8-fb25427cf8de@xen.org \
--to=julien@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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 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).