If there is no need for supporting multiple devices simultaneously, or need for
checksum, or some level of support for fault tolerance, then an MTL will be
enough.
george.
On Jun 16, 2011, at 09:47 , Peter Kjellström wrote:
> On Tuesday, June 14, 2011 06:25:52 PM Jeff Squyres wrote:
>> Thank
On Jun 16, 2011, at 3:47 AM, Peter Kjellström wrote:
>> I should say that if anyone is contemplating writing a new BTL, I'm happy
>> to get on the phone / webex with you for an intro to the OMPI code base,
>> point you in the right direction, etc. Ping me on/off list and we can
>> setup a time.
>
On Tuesday, June 14, 2011 06:25:52 PM Jeff Squyres wrote:
> Thanks Tim!
>
> I should say that if anyone is contemplating writing a new BTL, I'm happy
> to get on the phone / webex with you for an intro to the OMPI code base,
> point you in the right direction, etc. Ping me on/off list and we can
Thanks Tim!
I should say that if anyone is contemplating writing a new BTL, I'm happy to
get on the phone / webex with you for an intro to the OMPI code base, point you
in the right direction, etc. Ping me on/off list and we can setup a time.
Reading reading reading documentation is all well a
Hi Larry,
Good timing... Jeff Squyres just posted yesterday about this topic.
You can find his suggestions here:
http://www.open-mpi.org/community/lists/devel/2011/06/9366.php
-- Tim
On Tue, Jun 14, 2011 at 11:10 AM, Lawrence Stewart
wrote:
> I apologize for asking elementary questions, I have s
I apologize for asking elementary questions, I have spent some time looking
through the open-mpi.org site and the list archives, without notable success.
I am contemplating writing a btl component in order to make OpenMPI work on the
fos experimental message-based operating system under construc
If there is no objection I will commit this to the trunk next week.
On Sun, Dec 09, 2007 at 05:34:30PM +0200, Gleb Natapov wrote:
> Hi,
>
> Currently BTL has parameter btl_min_send_size that is no longer used.
> I want to change it to be btl_rndv_eager_limit. This new parameter will
> determine
On Wed, Dec 12, 2007 at 01:18:10PM -0800, Paul H. Hargrove wrote:
> Gleb Natapov wrote:
> > On Wed, Dec 12, 2007 at 02:03:02PM -0500, Jeff Squyres wrote:
> >
> >> On Dec 9, 2007, at 10:34 AM, Gleb Natapov wrote:
> >>
> >>
> >>> Currently BTL has parameter btl_min_send_size that is no longe
Gleb Natapov wrote:
On Wed, Dec 12, 2007 at 02:03:02PM -0500, Jeff Squyres wrote:
On Dec 9, 2007, at 10:34 AM, Gleb Natapov wrote:
Currently BTL has parameter btl_min_send_size that is no longer used.
I want to change it to be btl_rndv_eager_limit. This new parameter
will
determine
On Wed, Dec 12, 2007 at 02:03:02PM -0500, Jeff Squyres wrote:
> On Dec 9, 2007, at 10:34 AM, Gleb Natapov wrote:
>
> > Currently BTL has parameter btl_min_send_size that is no longer used.
> > I want to change it to be btl_rndv_eager_limit. This new parameter
> > will
> > determine a size of a
On Dec 9, 2007, at 10:34 AM, Gleb Natapov wrote:
Currently BTL has parameter btl_min_send_size that is no longer used.
I want to change it to be btl_rndv_eager_limit. This new parameter
will
determine a size of a first fragment of rendezvous protocol. Now we
use
btl_eager_limit to set its
Hi,
Currently BTL has parameter btl_min_send_size that is no longer used.
I want to change it to be btl_rndv_eager_limit. This new parameter will
determine a size of a first fragment of rendezvous protocol. Now we use
btl_eager_limit to set its size. btl_rndv_eager_limit will have to be
smaller
12 matches
Mail list logo
