Eugene Loh wrote:
Actually, there may be a more important issue here.
Currently, the PML chooses the BTL first. Once the BTL choice is
established, only then does the PML choose between sendi and send.
Currently, it's also the case that we're spending a lot of time in the
PML doing a bunch
Actually, there may be a more important issue here.
Currently, the PML chooses the BTL first. Once the BTL choice is
established, only then does the PML choose between sendi and send.
Currently, it's also the case that we're spending a lot of time in the
PML doing a bunch of stuff that's tot
Ken,
Your interpretation of the MPI standard is way too optimistic.
Unfortunately, there is no asynchronous progress (expect on very few
devices) in most of the MPI libraries. So, you should not expect the
non blocking send to complete, without going in some MPI calls
(MPI_Test as an exam
I'm running OpenMPI 1.2.6 under Red Hat Enterprise Linux Server
release 5.2 on an x86_64 cluster.
When I send a message with MPI_Isend I think it should eventually be
delivered (if I have a receive waiting), without my having to make any
other MPI calls. This appears to be guaranteed by the spec.
On Feb 23, 2009, at 12:14 , Eugene Loh wrote:
I'm a newbie and George is a veteran. So, this feels rather like
David and Goliath. (Hmm, David won and became king. Gee, I kinda
like that.) Anyhow...
That's an old story, we're living in modern times now ;)
George Bosilca wrote:
It d
I sent this to the users mailing list buy maybe this is a better place
for it. Can anyone help with this??
I'm trying to use the compiler_args field in the wrappers script to deal
with 32 bit compiles on our cluster.
I'm using Portland Group compilers and use the following for 32 bit
builds: -t
I'm a newbie and George is a veteran. So, this feels rather like David
and Goliath. (Hmm, David won and became king. Gee, I kinda like
that.) Anyhow...
George Bosilca wrote:
It doesn't sound reasonable to me. There is a reason for this, and I
think it's a good reason. The sendi function
On Mon, 23 Feb 2009, Jeff Squyres wrote:
On Feb 23, 2009, at 10:37 AM, Eugene Loh wrote:
I sense an opening here and rush in for the kill...
:-)
And, why does the PML pass a BTL argument into the sendi function? First,
the BTL argument is not typically used. Second, if the BTL sendi func
I notice that I'm getting a pile of trunk one-sided errors in
test_start1 and test_start3. "Errors" means "segv" in this scenario:
http://www.open-mpi.org/mtt/index.php?do_redir=960
I'm afraid that I don't have the cycles to follow up on this at the
moment, but I thought I'd pass the in
On Feb 23, 2009, at 11:24 AM, Brian W. Barrett wrote:
At a high level, it seems reasonable to me. I am not familiar
enough with the sendi code, however, to have a strong opinion either
way.
Ditto. George just had what sounds like a reasonable counter-
argument, though...
I'll back away
At a high level, it seems reasonable to me. I am not familiar enough with
the sendi code, however, to have a strong opinion either way.
Brian
On Mon, 23 Feb 2009, Jeff Squyres wrote:
Sounds reasonable to me. George / Brian?
On Feb 21, 2009, at 2:11 AM, Eugene Loh wrote:
What: Eliminate
It doesn't sound reasonable to me. There is a reason for this, and I
think it's a good reason. The sendi function work for some devices as
a fast path for sending data, when the network is not flooded.
However, in the case sendi cannot do the job we expect, the fact that
it return the descr
On Feb 23, 2009, at 10:37 AM, Eugene Loh wrote:
I sense an opening here and rush in for the kill...
:-)
And, why does the PML pass a BTL argument into the sendi function?
First, the BTL argument is not typically used. Second, if the BTL
sendi function wants to know what BTL it is,... uh
I sense an opening here and rush in for the kill...
And, why does the PML pass a BTL argument into the sendi function?
First, the BTL argument is not typically used. Second, if the BTL sendi
function wants to know what BTL it is,... uh, doesn't it already
know??? Doesn't a BTL know who it i
Sounds reasonable to me. George / Brian?
On Feb 21, 2009, at 2:11 AM, Eugene Loh wrote:
What: Eliminate the "descriptor" argument from sendi functions.
Why: The only thing this argument is used for is so that the sendi
function can allocate a descriptor in the event that the "send"
can
15 matches
Mail list logo
