From: Arjan van de Ven <arjan@infradead.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org,
Shawn Bohrer <shawn.bohrer@gmail.com>,
Jon Masters <jonathan@jonmasters.org>
Subject: Re: [PATCH 5/6] module: make modversion_info contain a pointer, not an array.
Date: Wed, 28 Jan 2009 14:41:14 -0800 [thread overview]
Message-ID: <20090128144114.4aeaa0ff@infradead.org> (raw)
In-Reply-To: <200901290859.40725.rusty@rustcorp.com.au>
On Thu, 29 Jan 2009 08:59:40 +1030
Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Thursday 29 January 2009 01:22:31 Arjan van de Ven wrote:
> > On Thu, 29 Jan 2009 00:05:52 +1030
> > Rusty Russell <rusty@rustcorp.com.au> wrote:
> >
> > >
> > > With allmodconfig (minus non-building modules) on 32-bit x86:
> > > Total size of modules before: 60009790 bytes
> > > Total size of modules after: 55927866 bytes
> > >
> > > Saving 7% of module size for CONFIG_MODVERSIONS=y; and these
> > > sections are kept resident as well.
> > >
> >
> > that reminds me.. can we just simplify MODVERSIONS to be a md5sum
> > (or sha1 whatver) of the .config file in the VERMAGIC ?
> > it's a lot more reliable in detecting incompatibilities, and a lot
> > less space consumed.
>
> Unfortunately people really seem to want the finer granularity that
> MODVERSIONS (sometimes) provides :( I've tried killing it off
> several times, and always failed.
but we could just stick the result in VERMAGIC right?
rather than tacking it to every symbol.
how you calculate the global checksum is almost a separate debate.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-01-28 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 13:35 [PATCH 5/6] module: make modversion_info contain a pointer, not an array Rusty Russell
2009-01-28 14:52 ` Arjan van de Ven
2009-01-28 22:29 ` Rusty Russell
2009-01-28 22:41 ` Arjan van de Ven [this message]
2009-01-29 7:44 ` Rusty Russell
2009-01-29 6:50 ` Jon Masters
2009-02-05 16:01 ` Shawn Bohrer
2009-02-07 2:24 ` Rusty Russell
2009-02-09 17:50 ` Shawn Bohrer
2009-02-10 3:27 ` Rusty Russell
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=20090128144114.4aeaa0ff@infradead.org \
--to=arjan@infradead.org \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=shawn.bohrer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.