On Fri, 8 Apr 2005, Peter W. Draper wrote:
> In general as you approach the 2Gb limit under i386 it seems that our
> programs behave quite differently. All too many seem to enter CPU bound
> states (this may be down to atask signal handling) the others generally
> make some garbled response showing a negative integer as the amount of
> memory not mapped, or crash.
>
> On the bright-side under x86_64, I have created and mapped in HDS
> components at addresses beyond 1.6Gb in an NDF, and GAIA has displayed an
> NDF of size 3.2Gb, nothing else seemed to want to look at that, however!
>
Won't some of this go away if the offseting code for mmap consistently
usese a BIGINT rather than an int? Also, do you want to comment on my
mmap64 suggestion?
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|