From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: rusty@rustcorp.com.au, jcm@jonmasters.org
Subject: depmod memory usage.
Date: Fri, 18 Nov 2011 15:35:49 -0500 [thread overview]
Message-ID: <20111118203548.GA17761@redhat.com> (raw)
I pulled out an older laptop last night to test something, and built
a kernel on it. When I did the make install part, the machine almost
ground to a halt.
It turned out that depmod used at peak 1.7GB of memory, (the laptop only had 1GB,
so it was swapping to the point of locking up interactivity for minutes
at a time). It took an hour to complete.
The config file is pretty pathological (it's a distro build, so tons of
modules -- http://codemonkey.org.uk/junk/fedora-config-x86-64)
It's been a while since I built on a machine with this amount of memory,
but it seems that depmod has taken a big step backwards as it used to
cope with this just fine.
This is with the m-i-t that shipped in Fedora 16 (3.16)
Dave
next reply other threads:[~2011-11-18 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 20:35 Dave Jones [this message]
2011-11-18 21:35 ` depmod memory usage Jon Masters
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=20111118203548.GA17761@redhat.com \
--to=davej@redhat.com \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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