Date: Thu, 21 Dec 2000 14:53:30 -0500 (EST) From: Leonard Wisniewski - Sun High Performance Computing Reply-To: Leonard Wisniewski - Sun High Performance Computing Subject: Two MPI I/O questions To: mpi-comments@XXXXXXXXXXXXX Cc: thakur@XXXXXXXXXXX X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc Sender: owner-mpi-comments@XXXXXXXXXXXXX I have two MPI I/O questions and I was hoping somebody on this alias would know one or both answers. 1) The MPI C++ bindings for SEEK_SET, SEEK_CUR, and SEEK_END will conflict when used in a source file in which /usr/include/fcntl.h is #include'd. I recall seeing some discussion on this topic, but I don't recall the resolution. 2) Shared file pointers. We currently implement them as a call to the run-time environment. Someone has recently asked me what would happen if the shared file pointer is used by an MPI client-server. In that case, a call to the run-time environment would not be sufficient, since the client and server may be operating on two different run-time environments. The suggestion was made that the shared file pointers be supported on a per-communicator basis. Before going from per-job to per-communicator, I was wondering if anyone else has thought about this and how to resolve it. Maybe it was not the intention of the spec for the shared file pointers to be used in a client-server scenario. Thanks in advance for any help on these questions! len --------------------------------------------------------------------------- Leonard F. Wisniewski, Ph.D. office: (781) 442-3144 HPC I/O team home: (978) 750-9082 Sun Microsystems, Computer Systems fax: (781) 442-1542 UBUR03-408, One Network Drive e-mail: lenbo@XXXXXXXXXXXX Burlington, MA 01803 ---------------------------------------------------------------------------