From: Chris Friesen <cfriesen@nortel.com>
To: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: buggy mlock() behaviour in 2.6.9 on ppc64?
Date: Wed, 02 Feb 2005 12:11:22 -0600 [thread overview]
Message-ID: <420117CA.8090507@nortelnetworks.com> (raw)
I've got a simple test app that tries to mmap() and mlock() an amount of
memory specified on the commandline.
If I specify more than the amount of physical memory in the system, I
get different behaviours between ppc and ppc64.
With the ppc kernel, my mmap() call will eventually fail and return
MAP_FAILED.
With the ppc64 kernel, however, the system hangs, and the fans speed
starts increasing. It seems like it doesn't realize that there is
simply no way that it will ever be able to succeed.
Is this expected behaviour for ppc64?
Chris
reply other threads:[~2005-02-02 18:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=420117CA.8090507@nortelnetworks.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox