On Fri, 3 Sep 2010, Jeff Squyres wrote:
On Sep 1, 2010, at 9:10 AM, Scott Atchley wrote:
I posted a patch for this on the ticket.
Will someone be committing this to SVN?
Done. Filed the CMRs to get this moved to 1.4.3 and 1.5.
I re-opened the ticket because just posting a patch to the
On Sep 3, 2010, at 8:19 AM, Jeff Squyres wrote:
> On Sep 1, 2010, at 9:10 AM, Scott Atchley wrote:
>
>> I posted a patch for this on the ticket.
>
> Will someone be committing this to SVN?
>
> I re-opened the ticket because just posting a patch to the ticket doesn't
> actually fix anything. :
On Sep 1, 2010, at 9:10 AM, Scott Atchley wrote:
> I posted a patch for this on the ticket.
Will someone be committing this to SVN?
I re-opened the ticket because just posting a patch to the ticket doesn't
actually fix anything. :-)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal info
Jeff,
I posted a patch for this on the ticket.
Scott
On Aug 26, 2010, at 10:10 AM, Scott Atchley wrote:
> Hi all,
>
> I compiled 1.4.3rc1 with MX 1.2.12 on RHEL 5.4 (2.6.18-164.el5). It does not
> like the memory manager and MX. Compiling using --without-memory-manager
> works fine. The outp
Hi all,
I compiled 1.4.3rc1 with MX 1.2.12 on RHEL 5.4 (2.6.18-164.el5). It does not
like the memory manager and MX. Compiling using --without-memory-manager works
fine. The output below is form the default configure (i.e.
--with-memory-manager).
Note, I still see unusual latencies for some te
