attached mail follows:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 01 December 2004 16:59, Yaakoub Y El Khamra wrote:
> This is what I got back from Jeff. Any ideas?
Jeff Squyres asked:
Does this application have a lot of pending non-blocking sends and
receives ongoing when the process fails? LAM *should* try to release
pinned memory in order to malloc/pin more, and therefore it should only
fail in this situation if all the pinned GM memory is actively being
used when you are trying to alloc more.
Jeff,
yes, exactly this is the case. The application tries to synchronise all
inter-processor boundaries at once, which should result in a large
burst of communication. The outstanding non-blocking sends and
receives should all be "active" in the sense that they are expected to
finish soon.
If GM has a problem with that, then this is possibly not the most
efficient way of handling this. Could the application be adapted so
that it does not hit GM's internal limitations, so that the application
will in the end run faster?
Thanks,
- -erik
- --
Erik Schnetter <schnetter_at_[hidden]> http://www.aei.mpg.de/~eschnett/
My email is as private as my paper mail. I therefore support encrypting
and signing email messages. Get my PGP key from www.keyserver.net.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBre4Xm3uiSwno3f0RAvOWAKCyHnqm+liAdIub/Y7uSL+Y1ig+vgCgrCqQ
3LML5dxbWqeCpbPC+d5j0wE=
=sR5S
-----END PGP SIGNATURE-----
|
