Re: [OMPI devel] Memory hooks stuff

> Who would be interested in discussing this stuff? (me, Brian, ? > someone from Sun?, ...?) > Me.

Re: [OMPI devel] plpa

Jeff, I prefer option 1. You should use your branch and merge it to the trunk. We shuold synchronize with the trunk and finish our work. The reason that we made the PLPA change in our brunch is that we needed it to our work. But we made it as a temporary change until the real thing will be in the

Re: [OMPI devel] PLPA ready?

are inter-dependent, can you send me a patch for the paffinity change? I'll apply it at the same time that I apply the new PLPA (later today). Thanks! On Feb 21, 2008, at 7:39 AM, Sharon Melamed wrote: > Yes, I think we should change paffinity.h and > paffinity_solaris_mo

Re: [OMPI devel] PLPA ready?

Yes, I think we should change paffinity.h and paffinity_solaris_module.c and paffinity_windows_module.c . I added those API's some time ago based on the plpa API's. Now, the plpa API has changed and no one uses those API's. (Except me and in the future, maybe Sun guys) So I don't see why not

Re: [OMPI devel] PLPA ready?

On Feb 20, 2008, at 7:53 AM, Sharon Melamed wrote: >> I guess I was torn between reporting num_processors/sockets and >> max_socket|core_id. Really, you need both, right? It is possible >> that the number of processors and/or sockets are not contiguous. > I need both *b

Re: [OMPI devel] PLPA ready?

On Feb 20, 2008 3:01 PM, Jeff Squyres <jsquy...@cisco.com> wrote: > On Feb 19, 2008, at 10:12 AM, Sharon Melamed wrote: > > I guess I was torn between reporting num_processors/sockets and > max_socket|core_id. Really, you need both, right? It is possible > that the

Re: [OMPI devel] PLPA ready?

e actually took some effort in PLPA to make a fairly neutral > API. > > > > On Feb 19, 2008, at 8:59 AM, Sharon Melamed wrote: > > > Jeff, > > > > The new PLPA fails in compilation. there is a need to change the > > paffinity API's: > > 1. max_processo

Re: [OMPI devel] PLPA ready?

Jeff, The new PLPA fails in compilation. there is a need to change the paffinity API's: 1. max_processor_id with one parameter --> get_processor_info with 2 parameters. 2. max_socket with one parameter --> get_socket_info with 2 parameters. 3. max_core with 2 parameters --> get_core_info with 3

Re: [OMPI devel] carto framework

All, If there are no objections, I will merge the carto branch to the trunk tomorrow. Sharon. 2008/1/14 Sharon Melamed <shar...@voltaire.com>: > > > > > I added a new framework to Open MPI called carto. You can brows the code in: > http://svn.open-mpi.org/s

[OMPI devel] carto framework

I added a new framework to Open MPI called carto. You can brows the code in: http://svn.open-mpi.org/svn/ompi/tmp-public/carto/. There are some explanations about the carto framework in the project wiki: https://svn.open-mpi.org/trac/ompi/wiki/OnHostTopologyDescription and you can read the

Re: [OMPI devel] ticket 1023

c launches the local procs outside of the orteds - is this true, or can I set affinity without going through the ODLS? That would be an issue for LANL, I believe. Thanks Ralph On 7/10/07 9:18 AM, "Sharon Melamed" <shar...@voltaire.com> wrote: > Hi Ralph, > > The responsib

[OMPI devel] ticket 1023

Hello All, In the recent few weeks I implemented ticket 1023 (https://svn.open-mpi.org/trac/ompi/ticket/1023 ). In a few words, the purpose of ticket 1023 is to expand the hostfile syntax to precisely specify slot location (in terms of virtual

[OMPI devel] Add a bug fix to 1.2.x version

Hi, I added a pkey value MCA parameter to the openIB BTL. (instead of using pkey index) Change set 14463 - https://svn.open-mpi.org/trac/ompi/changeset/14463. I would like to integrate this change to version 1.2.x. Thanks.

[OMPI devel] replace 'atoi' with 'strtol'

Hi, I want to add a patch to opal mca. This patch replaces an 'atoi' call with a 'strtol' call. If it's O.K with everyone I'll submit this patch by the end of the week. Index: opal/mca/base/mca_base_param.c === ---

[OMPI devel] (no subject)

Hi, I added an MCA parameter and I want the user to apply an Hex value to this parameter (0x...). In order to do so I needed to change the 'atoi' call in the mca_base_param.c file to 'strtol' call. My question is: Can this code run on all platforms? Index: opal/mca/base/mca_base_param.c