From: Gary Guo <gary@garyguo.net>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: "Lucas De Marchi" <lucas.demarchi@intel.com>,
"Kees Cook" <keescook@chromium.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, "Joel Stanley" <joel@jms.id.au>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Nicolas Schier" <nicolas@fjasle.eu>,
rust-for-linux@vger.kernel.org,
"Guo Zhengkui" <guozhengkui@vivo.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org,
"Julia Lawall" <Julia.Lawall@inria.fr>,
"Luis Chamberlain" <mcgrof@kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-modules@vger.kernel.org
Subject: Re: [PATCH] modpost: support arbitrary symbol length in modversion
Date: Thu, 19 Jan 2023 15:57:09 +0000 [thread overview]
Message-ID: <20230119155709.20d87e35.gary@garyguo.net> (raw)
In-Reply-To: <20230119151857.GQ16547@kitsune.suse.cz>
On Thu, 19 Jan 2023 16:18:57 +0100
Michal Suchánek <msuchanek@suse.de> wrote:
> On Thu, Jan 19, 2023 at 03:09:36PM +0000, Gary Guo wrote:
> > On Tue, 17 Jan 2023 11:22:45 -0800
> > Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> >
> > > And the additional 0's should compress well
> > > so I'm not sure the additional size is that much relevant here.
> >
> > I am not sure why compression is mentioned here. I don't think section
> > in .ko files are compressed.
>
> There is the option to compress the whole .ko files, and it's commonly
> used.
Hi Michal,
I am aware that there is an option but I am surprised to hear that it's
commonly used. I don't think that's enabled by default, and certainly
Debian/Ubuntu does not have it enabled.
Best,
Gary
next prev parent reply other threads:[~2023-01-19 15:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 16:11 [PATCH] modpost: support arbitrary symbol length in modversion Gary Guo
2023-01-12 21:40 ` Lucas De Marchi
2023-01-13 18:18 ` Gary Guo
2023-01-17 17:51 ` Michal Suchánek
2023-01-17 19:22 ` Lucas De Marchi
2023-01-18 7:01 ` Masahiro Yamada
2023-01-19 19:02 ` Lucas De Marchi
2023-01-19 19:19 ` Miguel Ojeda
2023-01-19 15:09 ` Gary Guo
2023-01-19 15:18 ` Michal Suchánek
2023-01-19 15:57 ` Gary Guo [this message]
2023-03-13 20:32 ` Andrea Righi
2023-03-13 21:48 ` Michal Suchánek
2023-03-13 21:53 ` Andrea Righi
2023-03-13 22:02 ` Michal Suchánek
2023-03-13 22:09 ` Andrea Righi
2023-03-14 14:38 ` Andrea Righi
2023-03-14 14:59 ` Andrea Righi
2023-03-15 0:15 ` Vincenzo Palazzo
2023-03-15 6:07 ` Andrea Righi
2023-03-15 16:18 ` Masahiro Yamada
2023-03-15 21:00 ` Andrea Righi
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=20230119155709.20d87e35.gary@garyguo.net \
--to=gary@garyguo.net \
--cc=Julia.Lawall@inria.fr \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=guozhengkui@vivo.com \
--cc=joel@jms.id.au \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lucas.demarchi@intel.com \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=msuchanek@suse.de \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=npiggin@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.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).