From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: mark.kettenis@xs4all.nl (Mark Kettenis)
Cc: eliz@gnu.org, gdb@sourceware.org
Subject: Re: bigcore.exp on 64-bit systems
Date: Sat, 13 Jan 2007 18:31:00 -0000 [thread overview]
Message-ID: <200701131831.l0DIVZWE032470@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <200701131450.l0DEoWpP029656@brahms.sibelius.xs4all.nl> from "Mark Kettenis" at Jan 13, 2007 03:50:32 PM
Mark Kettenis wrote:
> 2.6.16 certainly qualifies as modern. The idea is that the test will
> create a sparse core file, that will take up almost no disk space.
> But the fact that it takes more than 600 seconds to dump the core file
> (that's the cause of the SIGABRT timeout), suggests that it isn't
> doing that.
The problem I've seen on certain Linux kernel versions is that while
generating the core file, the kernel fully populates the page tables
spanning the (zero) heap allocated by the bigcore test.
This means that while it doesn't allocate memory (or disk space) for
the heap itself, it will allocate non-pageable memory for the page
tables, and if the heap gets to several TB, that means several GB
of page tables.
To circumvent this, I generally set a reasonable ulimit -v limit
before running the test suite on a 64-bit system.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-01-13 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 14:09 Eli Zaretskii
2007-01-13 14:16 ` Joel Brobecker
2007-01-13 14:50 ` Mark Kettenis
2007-01-13 15:16 ` Eli Zaretskii
2007-01-13 18:31 ` Ulrich Weigand [this message]
2007-01-13 19:23 ` Daniel Jacobowitz
2007-01-13 19:33 ` Mark Kettenis
2007-01-13 21:16 ` Eli Zaretskii
2007-01-13 15:21 ` Daniel Jacobowitz
2007-01-13 17:57 ` Eli Zaretskii
2007-01-13 18:01 ` Daniel Jacobowitz
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=200701131831.l0DIVZWE032470@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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