lkml.org 
[lkml]   [2005]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectbuggy mlock() behaviour in 2.6.9 on ppc64?
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:10    [W:0.021 / U:1.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site