From: "Adam J. Richter" <adam@yggdrasil.com>
To: jlnance@intrex.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Rusty's module talk at the Kernel Summit
Date: Mon, 1 Jul 2002 10:20:34 -0700 [thread overview]
Message-ID: <200207011720.KAA01499@adam.yggdrasil.com> (raw)
On Mon Jul 1 10:07:38 PDT 2002, Jim L. Nance wrote;
>On Mon, Jul 01, 2002 at 09:12:56AM -0700, Adam J. Richter wrote:
>> As an extereme illustration, imagine a module with 4095 bytes
>> of non-init data and 2 bytes of init data. With the .init section loaded,
>> the module will occupy two pages. Freeing the .init section will free
>> an entire page, making 4096 bytes available to the system, even though
>> only two bytes were in the .init section.
>
>Surly we can do better and just not generate .init sections for modules
>where the size would be smaller than a page. Is binutils capable of doing
>this given the proper linker script?
I wasn't talking specifically about modules smaller than a
page in that paragraph. I was talking about modules where the non-init
section ends toward the end of a page and appending the init
section would make it end more toward the begining of a (different) page.
I also wasn't talking about modifying binutils. binutils
already works fine with the present .text.init, .data.init, etc.
sections used in compiled-in kernel .o files (see include/linux/init.h)
I was talking about leaving some of this enabled for modules, and how
insmod could be changed to support it.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2002-07-01 17:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 17:20 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-11 5:44 Adam J. Richter
2002-07-11 5:07 Adam J. Richter
2002-07-04 17:24 Adam J. Richter
2002-07-11 2:48 ` Rusty Russell
2002-07-11 2:45 ` David S. Miller
2002-07-11 3:30 ` Alexander Viro
2002-07-11 5:13 ` Rusty Russell
2002-07-11 6:37 ` Alexander Viro
2002-07-11 7:14 ` Rusty Russell
2002-07-11 10:54 ` Daniel Phillips
2002-07-11 17:37 ` Roman Zippel
2002-07-11 18:01 ` Thunder from the hill
2002-07-11 18:50 ` Daniel Phillips
2002-07-17 18:16 ` bill davidsen
2002-07-17 19:35 ` Thunder from the hill
2002-07-11 18:28 ` Daniel Phillips
2002-07-11 19:48 ` Roman Zippel
2002-07-11 20:29 ` Daniel Phillips
2002-07-11 23:37 ` Alexander Viro
2002-07-12 1:54 ` Daniel Phillips
2002-07-12 3:53 ` Rusty Russell
2002-07-12 6:49 ` Kai Henningsen
2002-07-12 11:30 ` Roman Zippel
2002-07-12 0:00 ` Rusty Russell
2002-07-12 6:57 ` Kai Henningsen
2002-07-19 0:19 ` Richard Gooch
2002-07-22 16:29 ` Alexander Viro
2002-07-23 4:37 ` Richard Gooch
2002-07-11 4:02 ` Cort Dougan
2002-07-11 4:19 ` Arnaldo Carvalho de Melo
2002-07-11 4:46 ` Cort Dougan
2002-07-11 2:55 ` Arnaldo Carvalho de Melo
2002-07-11 3:01 ` Arnaldo Carvalho de Melo
2002-07-11 5:16 ` Rusty Russell
2002-07-03 15:53 Adam J. Richter
2002-07-03 17:07 ` Hugh Dickins
2002-07-03 18:46 ` Oliver Neukum
2002-07-03 23:25 ` Keith Owens
2002-07-03 23:09 ` Keith Owens
2002-07-03 7:31 Adam J. Richter
2002-07-03 8:54 ` Rogier Wolff
2002-07-03 12:27 ` Keith Owens
2002-07-03 14:10 ` Keith Owens
2002-07-01 16:12 Adam J. Richter
2002-07-01 17:02 ` jlnance
2002-07-03 5:01 ` Keith Owens
2002-07-01 8:45 Keith Owens
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=200207011720.KAA01499@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=jlnance@intrex.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®