Re: [OMPI devel] SM backing file size

2008-11-15 Thread Brooks Davis
On Sat, Nov 15, 2008 at 09:32:44AM -0800, Eugene Loh wrote: > Ralph Castain wrote: > >> I probably wasn't clear - see below >> >> On Nov 14, 2008, at 6:31 PM, Eugene Loh wrote: >> >>> Ralph Castain wrote: >>> I have two examples so far: 1. using a ramdisk, /tmp was set to 10MB.

Re: [OMPI devel] IPv6 support in OpenMPI?

2006-03-31 Thread Brooks Davis
On Sat, Apr 01, 2006 at 12:03:00AM +0200, Adrian Knoth wrote: > On Fri, Mar 31, 2006 at 11:06:55AM -0800, Brooks Davis wrote: > > > > One little problem here is that it is possible to disable the > > > IPv6-mapped IPv4 addresses at least under Linux and some BSD variants.

Re: [OMPI devel] IPv6 support in OpenMPI?

2006-03-31 Thread Brooks Davis
On Fri, Mar 31, 2006 at 06:53:05PM +0200, Christian Kauhaus wrote: > Adrian Knoth : > >(I really prefer the v6-mapped-v4 solution with a single > > socket, thus eliminating this problem) > > One little problem here is that it is possible to disable the > IPv6-mapped IPv4 addresses at least under L

[O-MPI devel] FreeBSD port committed

2005-10-27 Thread Brooks Davis
I've committed a port of Open MPI 1.0rc4 to the FreeBSD ports collection. That should at least generate wider exposure for the build and hopefully for the code a well. It will be regularly built on FreeBSD 4, 5, 6, and 7 under i386, ia64, amd64, alpha, sparc64, and ppc. -- Brooks -- Any statem

Re: [O-MPI devel] porting guide?

2005-10-13 Thread Brooks Davis
nd > the v1.0 branch. > > On Oct 12, 2005, at 4:20 PM, Brooks Davis wrote: > > > No testing yet, but I've modified configure.am and > > opal/util/stacktrace.c to work by probing for backtrace() and > > libexecinfo. The configure code is cribbed from the sched_ye

Re: [O-MPI devel] porting guide?

2005-10-12 Thread Brooks Davis
On Wed, Oct 12, 2005 at 11:07:51AM -0700, Brooks Davis wrote: > On Wed, Oct 12, 2005 at 08:58:30AM -0400, Jeff Squyres wrote: > > On Oct 12, 2005, at 12:54 AM, Brooks Davis wrote: > > > > >> Can you elaborate on why you needed that? If there's a problem with &g

Re: [O-MPI devel] porting guide?

2005-10-12 Thread Brooks Davis
On Wed, Oct 12, 2005 at 08:58:30AM -0400, Jeff Squyres wrote: > On Oct 12, 2005, at 12:54 AM, Brooks Davis wrote: > > >> Can you elaborate on why you needed that? If there's a problem with > >> the stacktrace stuff on BSD, I'd like to make it either disable

Re: [O-MPI devel] porting guide?

2005-10-11 Thread Brooks Davis
On Tue, Oct 11, 2005 at 11:20:57PM -0400, Jeff Squyres wrote: > On Oct 11, 2005, at 11:01 PM, Brooks Davis wrote: > > >> Of course, the 1.0 nightly for tomorrow morning will not have the fix > >> just yet. > > > > Thanks. With the following patchs an

Re: [O-MPI devel] porting guide?

2005-10-11 Thread Brooks Davis
On Mon, Oct 10, 2005 at 11:26:41PM -0500, Brian Barrett wrote: > On Oct 10, 2005, at 6:59 PM, Brooks Davis wrote: > > > The configure output ends with: > > > > ... > > config.status: creating test/util/Makefile > > config.status: creating include/ompi_config.h

Re: [O-MPI devel] porting guide?

2005-10-10 Thread Brooks Davis
On Mon, Oct 10, 2005 at 06:25:47PM -0500, Brian Barrett wrote: > On Oct 10, 2005, at 6:12 PM, Brooks Davis wrote: > > > I'm looking at porting Open MPI to FreeBSD and am trying to get a > > handle > > on the requirements. The issue I'm hitting so far is t

[O-MPI devel] porting guide?

2005-10-10 Thread Brooks Davis
I'm looking at porting Open MPI to FreeBSD and am trying to get a handle on the requirements. The issue I'm hitting so far is the opal timer code which won't finish configuration at the moment. Where is the API to implement documented? Is there an intent to implement a sub-optimal version with P