From: Jon Masters <jonathan@jonmasters.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Kyle McMartin <kyle@canonical.com>,
Christoph Pleger <Christoph.Pleger@cs.uni-dortmund.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Size of kernel modules
Date: Sat, 09 Jun 2007 12:14:06 -0400 [thread overview]
Message-ID: <1181405646.3306.27.camel@jcmlaptop> (raw)
In-Reply-To: <Pine.LNX.4.64.0706091558460.14652@fbirervta.pbzchgretzou.qr>
On Sat, 2007-06-09 at 15:59 +0200, Jan Engelhardt wrote:
> On Jun 9 2007 08:08, Jon Masters wrote:
> >
> >So I missed half of this conversation - you're saying that on a
> >CONFIG_DEBUG_KERNEL, you have such large .ko module files that depmod
> >segfaults? Can I get a core dump or any further information? :-)
>
> Just make sure your /lib/modules/<kernel> is like 300 megabytes or even
> more. Then depmod will clog up quite a lot memory already. (Taking a 256 mb ram
> machine for example, no swap or just very little.)
I'll go take a look at that.
Jon.
next prev parent reply other threads:[~2007-06-09 16:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 15:05 Size of kernel modules Christoph Pleger
2007-06-06 15:51 ` Jesper Juhl
2007-06-06 16:56 ` Jan Engelhardt
2007-06-06 17:17 ` Sam Ravnborg
2007-06-06 15:59 ` jimmy bahuleyan
2007-06-06 17:22 ` Sam Ravnborg
2007-06-06 18:40 ` Joseph Fannin
2007-06-08 3:44 ` Kyle McMartin
2007-06-08 12:40 ` Robert P. J. Day
2007-06-08 18:59 ` Chuck Ebbert
2007-06-09 7:55 ` Jan Engelhardt
2007-06-09 12:08 ` Jon Masters
2007-06-09 13:59 ` Jan Engelhardt
2007-06-09 16:14 ` Jon Masters [this message]
2007-06-09 18:56 ` Satyam Sharma
2007-06-10 13:13 ` Sergey Vlasov
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=1181405646.3306.27.camel@jcmlaptop \
--to=jonathan@jonmasters.org \
--cc=Christoph.Pleger@cs.uni-dortmund.de \
--cc=jengelh@computergmbh.de \
--cc=kyle@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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