All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
	kaos@ocs.com.au, linux-kernel@vger.kernel.org
Subject: Re: Suggestion for module .init.{text,data} sections
Date: Fri, 27 Apr 2001 09:14:46 -0400	[thread overview]
Message-ID: <3AE970C6.42695F2E@didntduck.org> (raw)
In-Reply-To: <200104270449.VAA05279@adam.yggdrasil.com> <20010427103519.E679@nightmaster.csn.tu-chemnitz.de>

Ingo Oeser wrote:
> 
> On Thu, Apr 26, 2001 at 09:49:05PM -0700, Adam J. Richter wrote:
> >       A while ago, on linux-kernel, we had a discussion about
> > adding support for __initdata and __init in modules.  Somebody
> > (whose name escapes me) had implemented it by essentially adding
> > a vmrealloc() facility in the kernel.  I think I've thought of a
> > simpler way, that would require almost no kernel changes.
> >
> [implementation details snipped]
> 
> While you are at this, you could make the .exit.{text,data}
> sections swappable for modules (by allocating swappable pages fro
> them?) and only mark them unswappable, while the module is
> exiting.
> 
> Rationale: A device needed for swaping will never call exit
> stuff, because it is still in use. So I see no obvious race here.
> 
> Regards

__exit functions and data are usually too small to make the effort worth
it.  __init functions and data on the other hand could be quite large,
if they contain firmware data for example.

--

				Brian Gerst

  reply	other threads:[~2001-04-27 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27  4:49 Suggestion for module .init.{text,data} sections Adam J. Richter
2001-04-27  8:35 ` Ingo Oeser
2001-04-27 13:14   ` Brian Gerst [this message]
2001-04-29  1:05   ` Pavel Machek
2001-04-29 20:40     ` Dominik Kubla

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=3AE970C6.42695F2E@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=adam@yggdrasil.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=kaos@ocs.com.au \
    --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 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.