Thread View: comp.hypercube
1 messages
1 total messages
Started by Thomas Paul Brisco
Fri, 07 Aug 1987 18:54
Re: ncube memory
Author: Thomas Paul Brisco
Date: Fri, 07 Aug 1987 18:54
Date: Fri, 07 Aug 1987 18:54
25 lines
1902 bytes
1902 bytes
In article <370@hubcap.UUCP> Lonnie R. Welch (welch-l@osu-eddie.UUCP) writes:
> I am trying to write a
> program that requires the use of several large data structures. It seems
> that the Host process can only have a data segment of size <= 64k. None of
> the variables in my program are larger than 64k, but the sum of the memory
> required by all the variables is > 64k. Has anyone else found this to be a
> problem? How did you get around this limitation?
You don't state whether you acutally need all of the variables
at a given time or not, but one of my tricks is to manually "data
swap" -- i.e. keep data that is not immediately needed on disk, and
malloc()/free() space as necesary to achieve you means.
One other, more crafty but harder, way is to split your
program into 2 processes and do the operations seperately, but
communicating (results) via pipes -- I've found this to be handy when
there are 2 large computations are involved (where both must be on the
host processor), but only the results are really necessary to proceed
in the original process. Look in n_frun, and see whether you really
need the computations locally, or whether they can be moved out of
(what I call) the "controlling process".
Tp.
- ARPA: Brisco@rutgers -
- UUCP: (ihnp4!ut-sally, allegra!packard) !caip!brisco -
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads