Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-devel] roadmap, XML/JSON/...
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2011-09-06 11:39:49


On Sep 6, 2011, at 11:25 AM, Brice Goglin wrote:

>> - I don't know where we ended up in the other thread: do we want JSON or no? If we can parse it easily without an external dependency, then I think it's worthwhile.
>
> I stopped working on JSON this to see where the idea of reimplementing
> our own XML parser would go.

Beyond your prior emails on this, any further thoughts? Especially if we restrict to ASCII-only?

>> - OTOH, JSON would be a new feature, and probably shouldn't be introduced after a x.y.0 release.
>
> Yeah but it's a new backend, it's supposed to not touch anything in the
> core and to not break other backends.

K, fair enough.

>> - I could bump OMPI to v1.3, but it's not as mature as 1.2.x, which just makes me a little nervous (the goal for the hwloc stuff is to bring it in late in the OMPI v1.5 series... but I've already got some feedback that there might be resistance to what we're proposing to use hwloc for in OMPI, so we'll see :-) ).
>
> Agreed, v1.3 is too young for OMPI. I am not sure many people already
> tried v1.3rc1. I wouldn't put it in OMPI before hwloc 1.3.1.

K.

-- 
Jeff Squyres
jsquyres_at_[hidden]
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/