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] lstopo-nox strikes back
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2012-04-25 10:55:02


On Apr 25, 2012, at 10:48 AM, Samuel Thibault wrote:

>> FWIW: Having lstopo plugins for output would obviate the need for having two executable names.
>
> Well, it seems overkill to me. It makes sense to me to have both
> xlstopo and lstopo.

Ick. FWIW, I dislike having two executables. I like having one executable that can adapt itself to whatever is loaded / available on the system. :-)

But if I'm in the minority, no problem...

If I'm not, I can work on a patch to see if it would be horribly disruptive...

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