- "Ralph Castain" wrote:
> Sounds like a problem in PLPA - I'll have to defer
> to them.
Understood, thanks for that update. I'll try and
find some time to look inside PLPA too.
> Our primary PLPA person is on vacation this week, so
> you might not hear back from him until later next wee
On Jul 15, 2009, at 3:57 PM, George Bosilca wrote:
Regarding the latency issue, there is not much to say about. The
platform we tested on is clearly older than what other people test on,
but this is all about. The two versions (before and after the data-
type move) have the same latency, there i
Thanks George!
On Jul 16, 2009, at 3:13 PM, bosi...@osl.iu.edu wrote:
Author: bosilca
Date: 2009-07-16 15:13:30 EDT (Thu, 16 Jul 2009)
New Revision: 21703
URL: https://svn.open-mpi.org/trac/ompi/changeset/21703
Log:
Get rid of the ompi_convertor.h header file. Replace all references
to ompi_
Yo Greg
Any way your user can send me the print statements? I can't find
anything wrong with the code - I'm wondering if he has some non-
printing character in there that is causing a problem.
Thanks
Ralph
On Jul 16, 2009, at 12:37 PM, Ralph Castain wrote:
Weird. It doesn't look like it is
r21701 is a bad fix. By definition, we now get #warnings in the build.
By the comment that you guys wrote in ompi_convertor.h, that header
file should not exist -- it should be removed and all calls to those
functions should be replaced with their updated interfaces.
On Jul 16, 2009, at
Even worse, I was trying to fix this by changing btl_sctp.c from
#include "opal/datatype/opal_convertor.h"
to
#include "ompi/datatype/ompi_convertor.h"
But then I get
#warning "This header file should only be included as a convenience.
Please use the opal_convert.h header, functions and mac
There was a missing header. 21701 should fixes the problem.
george.
On Jul 16, 2009, at 14:31 , Jeff Squyres wrote:
George --
This does not compile.
btl_sctp.c: In function `mca_btl_sctp_prepare_dst':
btl_sctp.c:339: error: implicit declaration of function
`ompi_datatype_type_lb'
btl_sct
Weird. It doesn't look like it is actually interleaving, does it? It
looks more like a leading tag was incorrectly inserted between the m
and i in "mixing" for some reason.
I'll take a look at the code to see what might have triggered that...
On Jul 16, 2009, at 12:16 PM, Greg Watson wrote:
George --
This does not compile.
btl_sctp.c: In function `mca_btl_sctp_prepare_dst':
btl_sctp.c:339: error: implicit declaration of function
`ompi_datatype_type_lb'
btl_sctp.c:339: error: `ompi_datatype_t' undeclared (first use in this
function)
btl_sctp.c:339: error: (Each undeclared ident
Ralph,
One of our users is seeing the following output with the XML option
enabled (1.3.3):
time_mix_freq = 17
Time mixing option:
avgfit -- time averaging
with timestep chosen to fit exactly into one day or
coupling interval
Averaging time steps are at step numbers2,17 each
day
Another way to do this which I am not sure makes sense is to just add
sizeof(mca_pml_ob1_hdr_t) to the btl_eager_limit passed into by the
user. Thus the defining the limit to be specifically for the user data
and not the internal headers
which the user may not have any inkling about. However,
I was playing around with some really silly fragment sizes (sub 72
bytes) when I ran into some asserts in the btl_openib_sendi. I traced
the assert to be caused by mca_pml_ob1_send_request_start_btl()
calculating the true eager_limit with the following line:
size_t eager_limit = btl->btl_ea
There are some mailing lists for PLPA at:
http://www.open-mpi.org/community/lists/plpa.php
--td
Ralph Castain wrote:
Sounds like a problem in PLPA - I'll have to defer to them. Our
primary PLPA person is on vacation this week, so you might not hear
back from him until later next week when he g
Sounds like a problem in PLPA - I'll have to defer to them. Our
primary PLPA person is on vacation this week, so you might not hear
back from him until later next week when he gets through his inbox
mountain.
PLPA may have its own mailing list too - not really sure.
On Jul 15, 2009, at 10:
Hi all,
I have been trying some simple code to write a file using Parallel I/O on
Open MPI. Here I specify the MPI_Info value as 0 and the execution
terminates with this messge for any number of processes:
*** An error occurred in MPI_File_open
*** on communicator MPI_COMM_WORLD
*** MPI_ERR_INFO:
Thanks a lot Pasha,
You saved lot of my time.
Thanks
Regards
Neeraj Chourasia (MTS)
Computational Research Laboratories Ltd.
(A wholly Owned Subsidiary of TATA SONS Ltd)
B-101, ICC Trade Towers, Senapati Bapat Road
Pune 411016 (Mah) INDIA
(O) +91-20-6620 9863 (Fax) +91-20-6620 9862
M: +91.922552
Hi,
You can select ib device used with openib btl by using follow parametres:
MCA btl: parameter "btl_openib_if_include" (current value: , data
source: default value)
Comma-delimited list of devices/ports to be
used (e.g. "mthca0,mthca1:2"; empty value means to
Eugene,
great, thank you very much!
Now we have also write access to the FAQs, so it's easier for us to make
changes on it.
Matthias
On Wed, 2009-07-15 at 09:17 -0700, Eugene Loh wrote:
> Done. Hit "reload" on the URL below, check out an SVN repository, or
> wait for these changes to be push
- "Ralph Castain" wrote:
> Looking at your command line, did you remember to set -mca
> mpi_paffinity_alone 1?
Ahh, no, sorry, still feeling my way with this..
> If not, we won't set affinity on the processes.
Now it fails immediately with:
Setting processor affinity failed
--> Ret
19 matches
Mail list logo
