[mpi3-coll] More on in-place
Torsten Hoefler
htor at cs.indiana.edu
Mon Feb 2 21:45:46 CST 2009
On Mon, Feb 02, 2009 at 11:31:32AM -0800, Adam Moody wrote:
> I think we need another statement about the in-place option in the text
> regarding buffer access. Something along the lines of:
>
> When using the "in-place" option, message buffers may function as both
> send and receive buffers. Such buffers should not be modified or
> accessed until the operation completes.
good point! I added: "When using the ``in place'' option, message buffers
function as both send and receive buffers. Such buffers should not be
modified or accessed until the operation completes."
> This is somewhat unique to NBC. However, this statement is necessary
> for blocking collectives in threaded environments, as well. Did the
> "Send buffer access" ticket resolve this? Either way, it might not hurt
> to reiterate this point in the NBC intro, since it is more likely to
> come up there.
uh well - collectives need more discussion anyway.
Best,
Torsten
--
bash$ :(){ :|:&};: --------------------- http://www.unixer.de/ -----
Torsten Hoefler | Postdoctoral Researcher
Open Systems Lab | Indiana University
150 S. Woodlawn Ave. | Bloomington, IN, 474045, USA
Lindley Hall Room 135 | +01 (812) 855-3608
More information about the mpiwg-coll
mailing list