that this should not a problem anymore. Commit 19314 fix
this for the trunk, while commit 19315 fix it for the upcoming 1.3.
Thanks again for your report.
george.
On Aug 7, 2008, at 1:21 AM, Dave Grote wrote:
Hi,
I've been enhancing my code and have started using the ni
Hi,
I've been enhancing my code and have started using the nice routine
alltoallw. The code works fine except that there seems to be a memory
leak in alltoallw. I've eliminated all other possible causes and have
reduced the code down to a bare minimum. I've included fortran source
code which
I have this same issue from a while ago. Search for "x11 forwarding" in
the archives. The solution I settled on is to use the -d option, the
debug option. With this option, mpirun will keep the ssh sessions open,
and so the X forwarding stays active. Note that you do get lots of
debugging out
Sorry - my mistake - I meant AlltoAllV, which is what I use in my code.
Ashley Pittman wrote:
On Thu, 2008-03-20 at 10:27 -0700, Dave Grote wrote:
After reading the previous discussion on AllReduce and AlltoAll, I
thought I would ask my question. I have a case where I have data
After reading the previous discussion on AllReduce and AlltoAll, I
thought I would ask my question. I have a case where I have data
unevenly distributed among the processes (unevenly means that the
processes have differing amounts of data) that I need to globally
redistribute, resulting in a
ly suggest doing
so until we get back to that area.
Just my $0.02.
Ralph
On 12/1/06 4:51 PM, "Dave Grote" wrote:
Is there a place where I can hack the openmpi code to force it to keep
the ssh sessions open without the -d option? I looked through some of
the code, inclu
lting
xterm and have them echo'd back correctly.
- Galen
On Dec 1, 2006, at 11:48 AM, Dave Grote wrote:
Thanks for the suggestion, but it doesn't fix my problem. I did the
same thing you did and was able to get xterms open when using the -d
option. But when I
able to type characters in the resulting
xterm and have them echo'd back correctly.
- Galen
On Dec 1, 2006, at 11:48 AM, Dave Grote wrote:
Thanks for the suggestion, but it doesn't fix my problem. I did the
same thing you did and was able to get xterms open whe
Have you tried adding "-d"?
Thanks,
Galen
On Nov 30, 2006, at 2:42 PM, Dave Grote wrote:
I don't think that that is the problem. As far as I can tell, the
DISPLAY environment variable is being set properly on the
reate the problem you are seeing.
I’ll have to chat with folks here to understand what part of the
environment we absolutely need to carry forward, and what parts we need
to “cleanse” before passing it along.
Ralph
On 11/30/06 10:50 AM, "Dave Grote" wrote:
I
issue with the X server (xorg) or with the version of linux,
so I am also seeking help from the person who maintains caos linux. If
it matters, the machine uses myrinet for the interconnects.
Thanks!
Dave
Galen Shipman wrote:
what does your command line look like?
- Galen
On Nov 29,
I cannot get X11 forwarding to work using mpirun. I've tried all of the
standard methods, such as setting pls_rsh_agent = ssh -X, using xhost,
and a few other things, but nothing works in general. In the FAQ,
http://www.open-mpi.org/faq/?category=running#mpirun-gui, a reference is
made to oth
I have attached a small program that when run on my machine produces the
error message below and locks up.
[node:06319] [mpool_gm_module.c:100] error(8) registering gm memory
I get the error when I run with 32 processors, but not with 4 (even if I
increase the loop count to 2). This
13 matches
Mail list logo
