mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wilson Li <yongshenglee@yahoo.com>
To: Samuel Masham <Samuel.Masham@jp.sony.com>,
	Bill Davidsen <davidsen@tmr.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Yamaguchi, Yohei" <Yohei.Yamaguchi@jp.sony.com>,
	Tim Bird <tim.bird@am.sony.com>
Subject: Re: Slow loading big kernel module in 2.6 on PPC platform
Date: Thu, 29 Sep 2005 19:57:36 -0700 (PDT)	[thread overview]
Message-ID: <20050930025736.63518.qmail@web34109.mail.mud.yahoo.com> (raw)
In-Reply-To: <200509291030.39024.Samuel.Masham@jp.sony.com>



--- Samuel Masham <Samuel.Masham@jp.sony.com> wrote:

> > Wilson Li wrote:
> > > Hi,
> > > 
> > > I am trying to port several third party kernel modules from
> > kernel
> > > 2.4 to 2.6 on a ppc (MPC824x) platform. For small size of
> > modules, it
> > > works perfectly in 2.6. But there's one huge kernel module
> which
> > size
> > > is about 2.7M bytes (size reported by lsmod after insmod), and
> it
> > > takes about 90 seconds to load this module before init_module
> > starts.
> > > I did not notice there's such obvious delay in 2.4 kernel.
> 
> I assume you are on a slow ppc32 platform.
> 
> The time taken is a function of the number of symbols, you can work
> around it 
> as shown in the patch below. Obviously this is just an example
> patch and is
> NOT signed off for anything but reading :)
> 
> I would really like do some work on a pre-link for modules but
> don't really know 
> where to start.
> 
> Any hints?
> 
> Samuel
> 
> ps Not subscribed, just  so please cc me
> 

Here's my two cents.

1. Add time-consuming get_plt_size() functionality to
scripts/mod/modpost.c (per arch), and calculate the size when
scripts/mod/modpost is called to generate mymodule.mod.c during
making of kernel module.

2. How to pass this info down to sys_init_module() in kernel? Maybe
we can add a special section in mymodule.mod.c. So this info will be
part of mymodule.ko and parsed by sys_init_module() later.

Then it won't make too much impact on the build process.

Sounds easy;-) Hopefully it'll work.

Wilson Li







	
		
______________________________________________________ 
Yahoo! for Good 
Donate to the Hurricane Katrina relief effort. 
http://store.yahoo.com/redcross-donate3/ 


  parent reply	other threads:[~2005-09-30  2:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29  1:30 Samuel Masham
2005-09-29 23:46 ` Wilson Li
2005-09-30  0:58   ` Wilson Li
2005-09-30  2:57 ` Wilson Li [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-28 19:29 Wilson Li
2005-09-28 19:53 ` linux-os (Dick Johnson)
2005-09-28 22:27   ` Wilson Li
2005-09-29 13:04     ` linux-os (Dick Johnson)
2005-09-29 23:50       ` Wilson Li
2005-09-30 15:46         ` linux-os (Dick Johnson)
2005-09-28 20:55 ` Bill Davidsen
2005-09-28 21:37   ` Wilson Li
2005-09-29  7:36     ` Arjan van de Ven

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=20050930025736.63518.qmail@web34109.mail.mud.yahoo.com \
    --to=yongshenglee@yahoo.com \
    --cc=Samuel.Masham@jp.sony.com \
    --cc=Yohei.Yamaguchi@jp.sony.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.bird@am.sony.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

all inboxes | Powered by JetHome®