Mmmm. Interesting idea... On Oct 3, 2014, at 3:55 AM, Marc-Andre Hermanns <[email protected]> wrote:
Hi all,
at the call we discussed that tools would have call the info function twice to make sure the name buffer is large enough to hold the full variable name.
Couldn't we define additional constants, such as MPI_T_PVAR_MAX_NAME_LEN, which indicate the maximum length a pvar name (in this example) can have. Then a tools can choose to pay in time (with two calls) or memory (with always allocating max memory) for a pvar name buffer.
This way we don't have to change the calls, and might mitigate the pain.
Cheers, Marc-Andre
PS: I would think this to be a different ticket. _Not_ 383 ... ;-) -- Marc-Andre Hermanns Jülich Aachen Research Alliance, High Performance Computing (JARA-HPC) German Research School for Simulation Sciences GmbH
Schinkelstrasse 2 52062 Aachen Germany
Phone: +49 241 80 99753 Fax: +49 241 80 6 99753 www.grs-sim.de/parallel email: [email protected]
_______________________________________________ mpiwg-tools mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
participants (1)
-
Jeff Squyres (jsquyres)