Yup. It works. Thanks! With r18470 it works even better!
Jon Mason wrote:
On Tue, May 20, 2008 at 03:44:41PM -0400, Pak Lui wrote:
Hi Jon,
This is CentOS 4.6 on Ranger. Sorry I didn't mention it. So what should
I do?
login3% more /etc/*release*
::
/etc/redhat-release
One more point that Pasha and I hashed out yesterday in IM...
To avoid the problem of posting a short handshake buffer to already-
existing SRQs, we will only do the extra handshake if there are PPRQ's
in receive_queues. The handshake will go across the smallest PPRQ,
and represent all QPs
Thanks,
Rich
On 5/20/08 10:37 PM, "Brad Benton" wrote:
>
>
> 2008/5/20 Richard Graham :
>> Brad,
>> Do you want these for bug fixes too ?
>
> I think that it's okay to check in small bug fixes without a ticket. I know
> this is a somewhat
And there's a typo in my first paragraph. The flag currently defaults to
1 (print the warning). It should be switched to 0 to turn off the
warning. Sorry for any confusion I might have caused -- I blame the lack
of caffeine in the morning.
Brian
On Wed, 21 May 2008, Pavel Shamis (Pasha)
On May 21, 2008, at 11:14 AM, Brian W. Barrett wrote:
I think having a parameter to turn off the warning is a great idea.
So
great in fact, that it already exists in the trunk and v1.2 :)!
Setting
the default value for the btl_base_warn_component_unused flag from 0
to 1
will have the
On Wed, 21 May 2008, Jeff Squyres wrote:
2. An out-of-the-box "mpirun a.out" will print warning messages in
perfectly valid/good configurations (no verbs-capable hardware, but
just happen to have libibverbs installed). This is a Big Deal.
Which is easily solved with a better error message,
So are you proposing to set btl_base_warn_component_unused to 0 or
something more BTL specific?
--td
Jeff Squyres wrote:
What: Change default in openib BTL to not complain if no OpenFabrics
devices are found
Why: Many linuxes are shipping libibverbs these days, but most users
still don't
As I know only Openib kernel drivers is installed by default with
distribution.
But the user level - libibverbs and other openib stuff is not installed
by default. User need go to the package manager and explicitly
select libibverb. So if user decided to install libibverbs he had
reasons for
One thing I should clarify -- the ibverbs error message from my
previous mail is a red herring. libibverbs prints that message on
systems where the kernel portions of the OFED stack are not installed
(such as the quick-n-dirty test that I did before -- all I did was
install libibverbs
Then we disagree on a core point. I believe that users should never have
something silently unexpected happen (like falling back to TCP from a high
speed interconnect because of a NIC reset / software issue). YOu clearly
don't feel this way. I don't really work on the project, but do have
Just want to make sure what I think I see is true:
Linux build. openib btl requires ptmalloc2 and ptmalloc2 requires posix
threads, is that correct?
On May 21, 2008, at 4:17 PM, Don Kerr wrote:
Just want to make sure what I think I see is true:
Linux build. openib btl requires ptmalloc2 and ptmalloc2 requires
posix
threads, is that correct?
ptmalloc2 is not *required* by the openib btl. But it is required on
Linux if you want to
On Wed, 21 May 2008, Jeff Squyres wrote:
On May 21, 2008, at 3:38 PM, Jeff Squyres wrote:
It would be great if libibverbs could return two different error
messages
- one for "there's no IB card in this machine" and one for "there's
an IB
card here, but we can't initialize it". I think that
On May 21, 2008, at 12:21 PM, Terry Dontje wrote:
So are you proposing to set btl_base_warn_component_unused to 0 or
something more BTL specific?
Probably something more btl-specific. The libibverbs-being-shipped-in-
main-line-Linux-distro's issue doesn't really affect other BTLs, so I
On Wed, 21 May 2008, Jeff Squyres wrote:
On May 21, 2008, at 4:17 PM, Don Kerr wrote:
Just want to make sure what I think I see is true:
Linux build. openib btl requires ptmalloc2 and ptmalloc2 requires
posix
threads, is that correct?
ptmalloc2 is not *required* by the openib btl. But it
On May 21, 2008, at 4:37 PM, Brian W. Barrett wrote:
ptmalloc2 is not *required* by the openib btl. But it is required on
Linux if you want to use the mpi_leave_pinned functionality. I see
one function call to __pthread_initialize in the ptmalloc2 code -- it
*looks* like it's a function of
On Wed, 21 May 2008, Jeff Squyres wrote:
I'm only concerned about the case where there's an IB card, the user
expects the IB card to be used, and the IB card isn't used.
Can you put in a site wide
btl = ^tcp
to avoid the problem? If the IB card fails, then you'll get
unreachable MPI
I would dearly like a week-long class on Open MPI -
what it is, does, how to build, parameter tweaking, etc.
Does anyone know if such a class exists *anywhere* ?
On May 21, 2008, at 5:02 PM, Brian W. Barrett wrote:
If this is true (for some reason I thought it wasn't), then I think
we'd
actually be ok with your proposal, but you're right, you'd need
something
new in the IB btl. I'm not concerned about the dual rail issue -- if
you're smart enough
Brian and I chatted a bit about this off-list, and I think we're in
agreement now:
- do not change the default value or meaning of
btl_base_want_component_unsed.
- major point of confusion: the openib BTL is actually fairly unique
in that it can (and does) tell the difference between
20 matches
Mail list logo