On Mon, Aug 08, 2005 at 07:44:48AM -0600, Ralph H. Castain wrote:
> Very interesting - it built fine for me (building static). However,
> the ns_base_nds.c file is "stale", so I just committed a "delete" of
> that file. It shouldn't have been building anyway as it isn't in the
> Makefile. My
Hello,
Why libibcm.so is now required to build openib module?
--
Gleb.
Do you want me to send it
to you?
>
> Tim
>
>
> Gleb Natapov wrote:
> >Hello Tim,
> >
> >On Thu, Aug 11, 2005 at 10:08:04AM -0600, Tim S. Woodall wrote:
> >
> >>Hello Gleb,
> >>
> >>A couple of general comments:
> >>
I can't compile today's svn code:
gcc -shared .libs/ptl_self.o .libs/ptl_self_component.o -pthread -lm
-lutil -Wl,-soname -Wl,mca_ptl_self.so -o .libs/mca_ptl_self.so
creating mca_ptl_self.la
(cd .libs && rm -f mca_ptl_self.la && ln -s ../mca_ptl_self.la
mca_ptl_self.la)
make[4]: Leaving
ptl/sm
> rm .deps/*
> make -k
> cd ../../../
>
>
I'll try that. Thank you.
> Brian
>
> On Aug 18, 2005, at 7:02 AM, Gleb Natapov wrote:
>
> > I can't compile today's svn code:
> >
> > gcc -shared .libs/ptl_self.o .libs/ptl_self_component
On Tue, Dec 06, 2005 at 11:07:44AM -0500, Brian Barrett wrote:
> On Dec 6, 2005, at 10:53 AM, Gleb Natapov wrote:
>
> > On Tue, Dec 06, 2005 at 08:33:32AM -0700, Tim S. Woodall wrote:
> >>> Also memfree hooks decrease cache efficiency, the better solution
> >
On Wed, Dec 07, 2005 at 10:40:51AM -0500, Brian Barrett wrote:
> Hopefully this made some sense. If not, on to the next round of e-
> mails :).
>
This made allot of sense. What is compiled by default now is malloc_hooks
I'll compile ptmalloc and play with it and may be then will be the next
On Thu, Dec 08, 2005 at 09:59:46AM -0500, Brian Barrett wrote:
> On Dec 8, 2005, at 9:27 AM, Gleb Natapov wrote:
>
> > On Wed, Dec 07, 2005 at 10:40:51AM -0500, Brian Barrett wrote:
> >> Hopefully this made some sense. If not, on to the next round of e-
> >> mail
Hello,
I found one more problem with ptmalloc and registration cache.
In arena.c:grow_heap() when heap is shrinking ptmalloc tries to be smart
and is using mmap() to change pages protection instead of mprotect() because
as a side effect mmap() drops underlying pages. In the case the area is
Hello,
btl_openib_reg_mru_len parameter is not propagated to rcache in current
trunk. I can control mru list length with rcache_rb_mru_len parameter,
but this parameter is global for all rcaches and it is not listed with
./bin/ompi_info -param all all.
--
Gleb.
Hello I have problem to compile latest trunk event after running
./autogen.sh.
I've got the following error:
gcc -DHAVE_CONFIG_H -I. -I../../../../ompi/orte/mca/ns
-I../../../include -I../../../include -I../../../../ompi/include
-I../../../../ompi -I../../.. -I../../../include
On Wed, Feb 08, 2006 at 07:08:35AM -0700, Ralph H. Castain wrote:
> Hi Gleb
>
> I just checked out another copy of the trunk and cannot replicate
> this problem. Could you take out a fresh trunk and see if it works
> for you? Could be something just got out of sync on your current
> checkout
On Thu, Mar 30, 2006 at 08:59:04AM -0700, Tim S. Woodall wrote:
> Gleb - we seem to be missing btl_mvapi_eager_rdma.h
>
Sory, should be OK now.
>
>
> g...@osl.iu.edu wrote:
> >Author: gleb
> >Date: 2006-03-30 07:55:31 EST (Thu, 30 Mar 2006)
> >New Revision: 9474
> >
> >Modified:
> >
This error is usually happens when libibverbs is dlopened without
RTLD_GLOBAL flag.
On Wed, Sep 06, 2006 at 03:05:39PM +0200, Ralf Wildenhues wrote:
> Hello,
>
> * Open MPI wrote on Wed, Sep 06, 2006 at 01:00:00PM CEST:
> > #334: Building with Libtool 2.1a fails to run OpenIB BTL
>
> >Are
On Wed, Sep 13, 2006 at 07:50:02PM +0530, Sunil Patil wrote:
> Hi,
>
> This is somewhat irrelevant question. It was said that in order delivery is
> a feature of Mellanox HCA and not part of IB spec. Is this true for UD type
> QPs also for which IB spec says that "in order delivery" is not
On Tue, Oct 31, 2006 at 09:35:05AM -0500, Donald Kerr wrote:
> Can someone explain to me the intended use of the following flag and/or
> all that it implies when set : MCA_BTL_DES_FLAGS_PRIORITY
>
I can explain how this flag is treated in openib BTL. We have two QPs
high and low priority. High
On Tue, Mar 06, 2007 at 10:10:44AM +0100, Bert Wesarg wrote:
> Fix the double-check locking[1] by defining the cls_initialized member to
> volatile.
>
> Greetings
>
> Bert Wesarg
>
> [1]: http://en.wikipedia.org/wiki/Double-checked_locking
Can you explain how the Java example from this page
On Tue, Mar 06, 2007 at 10:44:53AM +0100, Bert Wesarg wrote:
>
>
> Gleb Natapov wrote:
> > On Tue, Mar 06, 2007 at 10:10:44AM +0100, Bert Wesarg wrote:
> >> Fix the double-check locking[1] by defining the cls_initialized member to
> >> volatile.
> >
On Tue, Mar 06, 2007 at 11:24:06AM +0100, Bert Wesarg wrote:
> Hello,
>
> Gleb Natapov wrote:
> > If it does this after opal_atomic_lock() (which is explicit memory
> > barrier) then it is broken.
> Than, gcc 4.1.1 on the amd64 architecture is broken:
And can you repeat t
On Tue, Mar 06, 2007 at 12:13:16PM +0100, Bert Wesarg wrote:
> Gleb Natapov wrote:
> > On Tue, Mar 06, 2007 at 11:24:06AM +0100, Bert Wesarg wrote:
> >> Hello,
> >>
> >> Gleb Natapov wrote:
> >>> If it does this after opal_atomic_lock() (which is
m(). So if there's zero impact on
> > performance and it doesn't make the code [more] incredibly horrible
> > [than it already is], I'm in favor of this change.
> >
> >
> >
> > On May 17, 2007, at 7:00 AM, Gleb Natapov wrote:
> >
> >> Hi,
>
On Fri, May 25, 2007 at 09:31:33PM -0600, Galen Shipman wrote:
>
> On May 24, 2007, at 2:48 PM, George Bosilca wrote:
>
> > I see the problem this patch try to solve, but I fail to correctly
> > understand the implementation. The patch affect all PML and BTL in
> > the code base by adding
On Sun, May 27, 2007 at 10:19:09AM -0600, Galen Shipman wrote:
>
> > With current code this is not the case. Order tag is set during a
> > fragment
> > allocation. It seems wrong according to your description. Attached
> > patch fixes
> > this. If no specific ordering tag is provided to
On Sun, May 27, 2007 at 10:23:23AM -0600, Galen Shipman wrote:
> >>
> >>
> >> The problem is that MCA_BTL_DES_FLAGS_PRIORITY was meant to indicate
> >> that the fragment was higher priority, but the fragment isn't higher
> >> priority. It simply needs to be ordered w.r.t. a previous fragment,
>
On Sun, May 27, 2007 at 10:32:26AM -0600, Galen Shipman wrote:
> Can we get rid of mca_pml_ob1_send_fin_btl and just have
> mca_pml_ob1_send_fin? It seems we should just always send the fin
> over the same btl and this would clean up the code a bit.
Yes. It should be possible. I'll do that.
On Sun, May 27, 2007 at 10:34:33AM -0600, Galen Shipman wrote:
> Actually, we still need MCA_BTL_FLAGS_FAKE_RDMA , it can be used as
> a hint for components such as one-sided.
What is the purpose of the hint if it should be set for each interconnect.
Just assume that it is set and behave
Hi Galen,
On Sun, May 27, 2007 at 10:19:09AM -0600, Galen Shipman wrote:
>
> > With current code this is not the case. Order tag is set during a
> > fragment
> > allocation. It seems wrong according to your description. Attached
> > patch fixes
> > this. If no specific ordering tag is
On Thu, Jun 07, 2007 at 11:11:12AM -0400, George Bosilca wrote:
> ) I expect you to revise the patch in order to propose a generic
> solution or I'll trigger a vote against the patch. I vote to be
> backed out of the trunk as it export way to much knowledge from the
> Open IB BTL into the
On Thu, Jun 07, 2007 at 02:38:51PM -0400, George Bosilca wrote:
>
> On Jun 7, 2007, at 1:28 PM, Gleb Natapov wrote:
>
> >On Thu, Jun 07, 2007 at 11:11:12AM -0400, George Bosilca wrote:
> >>) I expect you to revise the patch in order to propose a generic
> >&g
Hello everyone,
I encountered a problem with openib on depend connection code. Basically
it works only by pure luck if you have more then one endpoint for the same
proc and sometimes breaks in mysterious ways.
The algo works like this: A wants to connect to B so it creates QP and sends it
to
On Wed, Jun 13, 2007 at 11:03:09AM -0400, Jeff Squyres wrote:
> Hey Gleb --
>
> Can you explain the rationale for this change? Is there a reason why
> the bandwidths reported by the IBV API are not sufficient? Are you
> trying to do creative things with multi-LID scenarios (perhaps QOS-
>
is OK with everyone how cares then I want this
change to go into 1.2 branch.
I don't care how this change will get to the trunk. I can use patched
version for a while. If you branch is in working state right now I can
merge this change into it tomorrow.
>
> Thanks,
>
> Galen
>
>
>
On Wed, Jun 13, 2007 at 12:45:01PM -0400, Jeff Squyres wrote:
> On Jun 13, 2007, at 12:08 PM, Gleb Natapov wrote:
>
> > I am not committing this yet. I want people to review my logic and the
> > patch. If the change is OK with everyone how cares then I want this
> > chan
On Wed, Jun 13, 2007 at 02:23:37PM -0400, Jeff Squyres wrote:
> On Jun 13, 2007, at 1:40 PM, Gleb Natapov wrote:
>
> >>> [snip]
> >>> coordination kind of teleconference. If people think this is a good
> >>> idea, I can setup the call.
> >>
>
On Wed, Jun 13, 2007 at 02:48:02PM -0400, Jeff Squyres wrote:
> On Jun 13, 2007, at 2:41 PM, Gleb Natapov wrote:
>
> >> Pasha tells me that the best times for Ishai and him are:
> >>
> >> - 2000-2030 Israel time
> >> - 1300-1300 US Eastern
> >
On Wed, Jun 13, 2007 at 07:08:51PM +0300, Gleb Natapov wrote:
> On Wed, Jun 13, 2007 at 09:38:21AM -0600, Galen Shipman wrote:
> > Hi Gleb,
> >
> > As we have discussed before I am working on adding support for
> > multiple QPs with either per peer resources or shared
On Wed, Jun 13, 2007 at 10:01:20PM -0400, Patrick Geoffray wrote:
> Jeff Squyres wrote:
> > Let's take a step back and see exactly what we *want*. Then we can
> > talk about how to have an interface for it.
>
> I must be missing something but why is the bandwidth/latency passed by
> the user
Hello,
Attached patch improves OB1 scheduling algorithm between multiple
links. Current algorithm perform very poorly if interconnects with very
different bandwidth values are used. For big message sizes it always
divide traffic equally between all available interconnects. Attached
patch change
k I have another idea. How about merging the ack with the
> next pipeline fragment for RDMA (except for the last fragment) ?
Can you elaborate? If you are talking about ACK from receiver on match
then we already merge it with first PUT message if possible.
>
> Thanks,
> george.
>
On Tue, Jun 26, 2007 at 05:42:05PM -0400, George Bosilca wrote:
> Gleb,
>
> Simplifying the code and getting better performance is always a good
> approach (at least from my perspective). However, your patch still
> dispatch the messages over the BTLs in a round robin fashion, which
>
Nobody except George haven't commented/complained about this patch, so I
assume everybody except George are OK with it. And from George mails I
don't understand if he is OK with me applying it to the trunk and he simply
thinks that further work should be done in this area. So I'll ask him
; On Jun 28, 2007, at 10:06 AM, Gleb Natapov wrote:
>
> >Nobody except George haven't commented/complained about this patch,
> >so I
> >assume everybody except George are OK with it. And from George mails I
> >don't understand if he is OK with me applying it to the tr
On Fri, Jul 06, 2007 at 06:36:13PM -0400, Tim Prins wrote:
> While looking into another problem I ran into an issue which made ob1
> segfault
> on me. Using gm, and running the test test_dan1 in the onesided test suite,
> if I limit the gm freelist by too much, I get a segfault. That is,
>
>
On Sun, Jul 08, 2007 at 12:41:58PM -0400, Tim Prins wrote:
> On Sunday 08 July 2007 08:32:27 am Gleb Natapov wrote:
> > On Fri, Jul 06, 2007 at 06:36:13PM -0400, Tim Prins wrote:
> > > While looking into another problem I ran into an issue which made ob1
> > > segfault o
On Mon, Jul 09, 2007 at 10:41:52AM -0400, Tim Prins wrote:
> Gleb Natapov wrote:
> > On Sun, Jul 08, 2007 at 12:41:58PM -0400, Tim Prins wrote:
> >> On Sunday 08 July 2007 08:32:27 am Gleb Natapov wrote:
> >>> On Fri, Jul 06, 2007 at 06:36:13PM -0400, Tim Pri
On Wed, Jul 11, 2007 at 01:17:02PM +0200, Christoph Niethammer wrote:
> Hello,
>
>
> Since some time I'm testing Open MPI at the HRLS. My main topic there is the
> thread support of Open MPI.
>
> Some time ago I found a segmentation fault when running the svn-trunk
> Version.
> Thanks to the
On Thu, Jul 12, 2007 at 03:04:01PM -0600, Ralph H Castain wrote:
> As always, any thoughts/suggestions are welcomed.
>
I hope Sharon's work on process affinity will be merged into the trunk
before this works begins and functionality will be preserved during the
work.
--
On Sat, Jul 14, 2007 at 01:16:42PM -0400, George Bosilca wrote:
> Instead of failing at configure time, we might want to disable the
> threading features and the shared memory device if we detect that we
> don't have support for atomics on a specified platform. In a non
> threaded build, the
On Wed, Jul 18, 2007 at 07:48:17AM -0600, Ralph H Castain wrote:
> I believe that was fixed in r15405 - are you at that rev level?
I am on the latest revision.
>
>
> On 7/18/07 7:27 AM, "Gleb Natapov" <gl...@voltaire.com> wrote:
>
> > Hi,
> >
On Wed, Jul 18, 2007 at 09:08:47AM -0600, Ralph H Castain wrote:
> But this will lockup:
>
> pn1180961:~/openmpi/trunk rhc$ mpirun -n 1 -host pn1180961 printenv | grep
> LD
>
> The reason is that the hostname in this last command doesn't match the
> hostname I get when I query my interfaces, so
On Wed, Jul 18, 2007 at 09:08:38PM +0300, Gleb Natapov wrote:
> On Wed, Jul 18, 2007 at 09:08:47AM -0600, Ralph H Castain wrote:
> > But this will lockup:
> >
> > pn1180961:~/openmpi/trunk rhc$ mpirun -n 1 -host pn1180961 printenv | grep
> > LD
> >
&g
gt; But it *does* provide an LD_LIBRARY_PATH that is pointing to your
> >>>> openmpi
> >>>> installation - it says it did it right here in your debug output:
> >>>>
> >>>>>>> [elfit1:14752] pls:rsh: reset LD_LIB
On Tue, Jul 24, 2007 at 11:20:11AM -0300, Lisandro Dalcin wrote:
> On 7/23/07, Jeff Squyres wrote:
> > Does anyone have any opinions on this? If not, I'll go implement
> > option #1.
>
> Sorry, Jeff... just reading this. I think your option #1 is the
> better. However, I
On Thu, Jul 26, 2007 at 04:29:40PM +0300, Gleb Natapov wrote:
> On Thu, Jul 26, 2007 at 09:12:26AM -0400, Jeff Squyres wrote:
> > I got a problem in MTT runs last night with the openib BTL w.r.t.
> > credits:
> >
> > [...lots of IMB output...]
> > #bytes
On Mon, Aug 06, 2007 at 09:53:20AM -0400, Bill Wichser wrote:
> We have run across an issue, probably more related to openib than to
> openmpi but don't know how to resolve.
>
> Linux kernel - 2.6.9-55.0.2.ELsmp x86_64
fork (and thus system()) is not supported by openib in this kernel.
To get
so the first macro just sets up the convertor, the second populates
> all the rest of the request state in the case that we will need it
> later because the fragment doesn't hit the wire.
> +++
> We all agreed.
>
On Mon, Aug 13, 2007 at 03:59:28PM -0400, Richard Graham wrote:
>
>
>
> On 8/13/07 3:52 PM, "Gleb Natapov" <gl...@voltaire.com> wrote:
>
> > On Mon, Aug 13, 2007 at 09:12:33AM -0600, Galen Shipman wrote:
> > Here are the
> > items we hav
Is this trunk or 1.2?
On Wed, Aug 29, 2007 at 09:40:30AM -0400, Terry D. Dontje wrote:
> I have a program that does a simple bucket brigade of sends and receives
> where rank 0 is the start and repeatedly sends to rank 1 until a certain
> amount of time has passed and then it sends and all done
Hi,
opal_atomic_lifo implementation suffers from ABA problem.
Here is the code for opal_atomic_lifo_pop:
1 do {
2 item = lifo->opal_lifo_head;
3 if( opal_atomic_cmpset_ptr( &(lifo->opal_lifo_head),
4 item,
5
On Thu, Sep 06, 2007 at 06:50:43AM -0600, Ralph H Castain wrote:
> WHAT: Decide upon how to handle MPI applications where one or more
> processes exit without calling MPI_Finalize
>
> WHY:Some applications can abort via an exit call instead of
> calling MPI_Abort when a
On Tue, Sep 11, 2007 at 10:14:30AM -0400, George Bosilca wrote:
> Gleb,
>
> This patch is not correct. The code preventing the registration of the same
> communicator twice is later in the code (same file in the function
> ompi_comm_register_cid line 326). Once the function
on
> the same communicator, it won't work.
Correct, but this is not what happens with mt_coll test. mt_coll calls
commdup on the same communicator in different threads concurrently, but
we handle this case inside ompi_comm_nextcid().
>
>
> Gleb Natapov wrote:
> > On T
On Tue, Sep 11, 2007 at 11:30:53AM -0400, George Bosilca wrote:
>
> On Sep 11, 2007, at 11:05 AM, Gleb Natapov wrote:
>
>> On Tue, Sep 11, 2007 at 10:54:25AM -0400, George Bosilca wrote:
>>> We don't want to prevent two thread from entering the code is same time.
>
George,
In the comment you are saying that "a message for a not yet existing
communicator can happen". Can you explain in what situation it can
happen?
Thanks,
--
Gleb.
collective is executed on old communicator after setup of a new
>> cid. Is this not enough to solve the problem? Some ranks may leave
>> this collective call earlier than others, but none can leave it before
>> all ranks enter it and at this stage new communicator is already ex
On Wed, Sep 19, 2007 at 10:26:15AM -0400, Dan Lacher wrote:
> In doing some runs with the osu_bibw test on a single node, we have
> found that it hands when using the trunk for message sizes 2097152 or
> larger unless the mpool_sm_min_size is set to a number larger than the
> message size. We
On Fri, Oct 05, 2007 at 09:43:44AM +0200, Jeff Squyres wrote:
> David --
>
> Gleb and I just actively re-looked at this problem yesterday; we
> think it's related to https://svn.open-mpi.org/trac/ompi/ticket/
> 1015. We previously thought this ticket was a different problem, but
> our
Hi,
Each time a someone needs to wait for request completion he
implements the same piece of code. Why not put this code into
inline function and use it instead. Look at the included patch, it
moves the common code into ompi_request_wait_completion() function.
Does somebody have any objection
laces :)
>
>
> On Oct 15, 2007, at 10:27 AM, Gleb Natapov wrote:
>
> > Hi,
> >
> >Each time a someone needs to wait for request completion he
> > implements the same piece of code. Why not put this code into
> > inline fun
on problem the fix to the problem will be a couple of lines of
code.
>
> - Galen
>
>
>
> On 10/11/07 11:26 AM, "Gleb Natapov" <gl...@voltaire.com> wrote:
>
> > On Fri, Oct 05, 2007 at 09:43:44AM +0200, Jeff Squyres wrote:
> >> David --
> &
On Wed, Oct 24, 2007 at 08:01:44PM -0400, Jeff Squyres wrote:
> My proposal is that the "connect" field can be added to the INI file
> and take a comma-delimited list of values of acceptable CPCs for a
> given device. For example, the ConnectX HCA can take the following
> value:
>
>
On Thu, Oct 25, 2007 at 10:55:25AM -0400, Jeff Squyres wrote:
> On Oct 25, 2007, at 10:35 AM, Gleb Natapov wrote:
>
> > I don't think xrc should be used by default even if HW supports it.
> > Only if
> > special config option is set xrc should be attempted.
>
&
Hi Brian,
Is there a special reason why you call btl functions directly instead
of using bml wrappers? What about applying this patch?
diff --git a/ompi/mca/osc/rdma/osc_rdma_component.c
b/ompi/mca/osc/rdma/osc_rdma_component.c
index 2d0dc06..302dd9e 100644
---
On Thu, Nov 01, 2007 at 11:15:21AM -0400, Don Kerr wrote:
> How would the openib btl handle the following scenario:
> Two nodes, each with two ports, all ports are on the same subnet and switch.
>
> Would striping occur over 4 connections or 2?
Only two connections will be created.
>
> If 2 is
On Wed, Nov 07, 2007 at 01:16:04PM -0500, George Bosilca wrote:
>
> On Nov 7, 2007, at 12:51 PM, Jeff Squyres wrote:
>
>>> The same callback is called in both cases. In the case that you
>>> described, the callback is called just a little bit deeper into the
>>> recursion, when in the "normal
On Wed, Nov 07, 2007 at 11:25:43PM -0500, Patrick Geoffray wrote:
> Richard Graham wrote:
> > The real problem, as you and others have pointed out is the lack of
> > predictable time slices for the progress engine to do its work, when relying
> > on the ULP to make calls into the library...
>
>
Sorry I missed a mail with the question.
On Mon, Nov 12, 2007 at 06:03:07AM -0500, Jeff Squyres wrote:
> On Nov 9, 2007, at 1:24 PM, Don Kerr wrote:
>
> > both, I was thinking of listing what I think are multi-rail
> > requirements
> > but wanted to understand what the current state of things
On Wed, Nov 14, 2007 at 06:44:06AM -0800, Tim Prins wrote:
> Hi,
>
> The following files bother me about this commit:
> trunk/ompi/mca/btl/sctp/sctp_writev.c
> trunk/ompi/mca/btl/sctp/sctp_writev.h
>
> They bother me for 2 reasons:
> 1. Their naming does not follow the prefix rule
> 2.
On Fri, Nov 16, 2007 at 11:36:39AM -0800, Jeff Squyres wrote:
> 1. Mon, 26 Nov, 10am US East, 7am US Pacific, 5pm Israel
> 2. Mon, 26 Nov, 11am US East, 8am US Pacific, 6pm Israel
> 3. Thu, 29 Nov, 10am US East, 7am US Pacific, 5pm Israel
> 4. Thu, 29 Nov, 11am US East, 8am US Pacific, 6pm Israel
On Fri, Nov 30, 2007 at 02:06:02PM -0500, Jeff Squyres wrote:
> Are any of the XRC tmp SVN branches still relevant? Or have they now
> been integrated into the trunk?
>
> I ask because I see 4 XRC-related branches out there under /tmp and /
> tmp-public.
They are not relevant any more. I'll
On Thu, Dec 06, 2007 at 09:46:45AM -0500, Tim Prins wrote:
> Also, when we are using threads, there is a case where we do not
> decrement the signaled count, in condition.h:84. Gleb put this in in
> r9451, however the change does not make sense to me. I think that the
> signal count should
On Wed, Dec 05, 2007 at 02:45:17PM -0500, Tim Mattox wrote:
> Hello,
> It appears that sometime after r16777, and by r16799, that something
> was broken on the trunk's openib support for 32-bit builds.
> The 64-bit tests all seem normal, as well as the 32-bit & 64-bit tests on
> the 1.2 branch on
Hi everybody,
I committed changes to BTL interface. Two new parameters are now
provided to descriptor allocation: endpoint and flags. I did my best to
change all in tree BTLs, but I can't compile all of them, so compilation
problems are possible. Can everybody test that the BTLs they care about
On Tue, Dec 11, 2007 at 10:27:55AM -0500, Tim Prins wrote:
> My understanding was that this behavior was not right, but upon further
> inspection of the pthreads documentation this behavior seems to be
> allowable.
>
I think that Open MPI does not implement condition variable in the strict
Hi,
I did a rewrite of matching code in OB1. I made it much simpler and 2
times smaller (which is good, less code - less bugs). I also got rid
of huge macros - very helpful if you need to debug something. There
is no performance degradation, actually I even see very small performance
; >
> > Rich
> >
> >
> > On 12/11/07 10:54 AM, "Gleb Natapov" <gl...@voltaire.com> wrote:
> >
> >> Hi,
> >>
> >>I did a rewrite of matching code in OB1. I made it much simpler and 2
> >> t
On Tue, Dec 11, 2007 at 08:16:07PM -0500, Jeff Squyres wrote:
> Isn't there a better way somehow? Perhaps we should have "select"
> call *all* the functions and accept back a priority. The one with the
> highest priority then wins. This is quite similar to much of the
> other selection
On Wed, Dec 12, 2007 at 03:37:26PM +0200, Pavel Shamis (Pasha) wrote:
> Gleb Natapov wrote:
> > On Tue, Dec 11, 2007 at 08:16:07PM -0500, Jeff Squyres wrote:
> >
> >> Isn't there a better way somehow? Perhaps we should have "select"
> >> call *al
On Wed, Dec 12, 2007 at 04:08:31PM +0200, Pavel Shamis (Pasha) wrote:
> Gleb Natapov wrote:
>> On Wed, Dec 12, 2007 at 03:37:26PM +0200, Pavel Shamis (Pasha) wrote:
>>
>>> Gleb Natapov wrote:
>>>
>>>> On Tue, Dec 11, 2007 at 08:16:07PM -0500,
the SCTP BTL is being built? What kind of
> environment is it?
Red Hat Enterprise Linux AS release 4 (Nahant Update 5)
# rpm -qa | grep sctp
lksctp-tools-devel-1.0.2-6.4E.1
lksctp-tools-doc-1.0.2-6.4E.1
lksctp-tools-1.0.2-6.4E.1
>
>
>
> On Dec 12, 2007, at 9:38 AM, Gleb Natapov
On Wed, Dec 12, 2007 at 10:31:37AM -0500, Jeff Squyres wrote:
> I'd be in favor of setting the TCP exclusivity to LOW+100 and setting
> SCTP exclusivity to LOW.
Fine with me.
>
>
> On Dec 12, 2007, at 10:07 AM, Gleb Natapov wrote:
>
> > On Wed, Dec 12, 2007 at 10:02:
ng it w/o some very
> > strong
> > reasons. Not apposed, just very cautious.
> >
> > Rich
> >
> >
> > On 12/11/07 11:47 AM, "Gleb Natapov" <gl...@voltaire.com> wrote:
> >
> >> On Tue, Dec 11, 2007 at 08:36:42AM -0800, Andrew Friedley
On Wed, Dec 12, 2007 at 03:52:17PM -0500, Jeff Squyres wrote:
> On Dec 12, 2007, at 3:20 PM, Gleb Natapov wrote:
>
> >> How about making a tarball with this patch in it that can be thrown
> >> at
> >> everyone's MTT? (we can put the tarball on www.open-mpi.org
On Wed, Dec 12, 2007 at 03:10:10PM -0600, Brian W. Barrett wrote:
> On Wed, 12 Dec 2007, Gleb Natapov wrote:
>
> > On Wed, Dec 12, 2007 at 03:46:10PM -0500, Richard Graham wrote:
> >> This is better than nothing, but really not very helpful for looking at the
> >>
On Thu, Dec 13, 2007 at 10:49:45AM +0200, Pavel Shamis (Pasha) wrote:
>> Because we want to support mixed setups and create XRC between nodes that
>> support it and RC between all other nodes.
>>
> Ok, sounds reasonable for me. Just need make sure that the parameters name
> will be user
also be good - actually better than hoping that one will hit out-of-order
> situations.
>
> Rich
>
>
> On 12/14/07 2:20 AM, "Gleb Natapov" <gl...@voltaire.com> wrote:
>
> > On Thu, Dec 13, 2007 at 06:16:49PM -0500, Richard Graham wrote:
> >> The
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 n
On Sat, Dec 15, 2007 at 08:27:29AM -0500, Jeff Squyres wrote:
> It doesn't look like this component is used anymore
> (it's .ompi_ignore'd).
>
> Anyone object to svn rm'ing it on the trunk?
>
Not me.
--
Gleb.
On Thu, Dec 13, 2007 at 08:04:21PM -0500, Richard Graham wrote:
> Yes, should be a bit more clear. Need an independent way to verify that
> data is matched
> in the correct order sending this information as payload is one way to do
> this. So,
> sending unique data in every message, and
On Mon, Dec 17, 2007 at 10:53:26AM -0500, Jeff Squyres wrote:
> Gleb -
>
> Is this picture of the v1.3 long message params accurate? (see attached)
Yes.
--
Gleb.
1 - 100 of 141 matches
Mail list logo