the way progress is done in the non-threaded case, adds a progress
thread for the threaded progress case (which should be made to use
George's progress engine when it is ready), and fixes some bugs with
request handling, especially with freeing requests (IO requests, that
is).
This commit was SVN r4332.
support is included because ROMIO is inherently thread-unsafe.
One possible way to have true asynchronous progress would be to use a
progress thread that wakes up and polls at some frequency when there
are non-blocking IO requests pending. This is pretty icky, though --
it should definitely have an MCA parameter to enable/disable this
functionality, as well as another to control the polling frequency.
This also strengthens the argument that we need a v2 of the io
framework -- one that is not designed to exclusively support ROMIO --
one that does something unimaginably "better" for the parallel MPI-2
IO interface. :-)
This commit was SVN r3786.
thingy needs to go on the *declaration*, not the *definition*. Well,
at least this was all done en masse and via an automated mechanism, so
total time wasted was only about 15 minutes...
This commit was SVN r2858.
includes the romio component. Only blocking operations are supported
-- non-blocking stuff is pending some changes in the top-level
progression engine, and some threaded issues need to be worked out.
This commit was SVN r2655.
- Mark those who are still not yet implemented:
- return an error
- have a grep-able string indicating that they are not yet
implemented
- ensure every function checks for init/finalize
- add more error checking to a bunch of functions
- unify the error checking -- it reflected about 3 different
[previous] error checking styles and MPI exception invocation styles
This commit was SVN r1817.
