[Beowulf] NASTRAN on cluster
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Greg Lindahl lindahl at pathscale.comTue Apr 12 11:53:00 PDT 2005
- Previous message: [Beowulf] NASTRAN on cluster
- Next message: [Beowulf] Eclipse For Clusters
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Apr 12, 2005 at 09:32:02AM -0700, Roland Krause wrote: > Finally the whole problem is history with the arrival of 2.6.9 where > changes to the kernel were made so that the memory spaces now grow > towards each other from opposite sides so that one now can avoid these > tricks allthogether, at least on 64bit machines :-) This isn't quite right. There are *3* things that grow: heap, mmap, and stack. What 2.6.9 does is use your maximum stack limit to move mmap as far from the heap as possible. So if you have an unlimited stacksize (common for Fortran users), you still have the same old issue. 2.6.9 is more clever for programs which use limited amounts of stack; that's common in C programs, but not most Fortran programs. In 64 bits, this was never an issue, because there's so much address space available: you'll run out of physical memory long before mmap, heap, or stack can collide. -- greg
- Previous message: [Beowulf] NASTRAN on cluster
- Next message: [Beowulf] Eclipse For Clusters
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
