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] [hwloc-svn] svn:hwloc r5299 - in branches/bgq: config include/private src
From: Brice Goglin (Brice.Goglin_at_[hidden])
Date: 2013-02-08 07:32:51


Le 08/02/2013 13:26, Samuel Thibault a écrit :
> Brice Goglin, le Fri 08 Feb 2013 13:23:33 +0100, a écrit :
>> Le 08/02/2013 12:52, Samuel Thibault a écrit :
>>> svn-commit-mailer_at_[hidden], le Fri 08 Feb 2013 12:02:18 +0100, a écrit :
>>>> Everything is hardwired in the backend, all nodes are the same.
>>> Would it be possible to check some file in /proc or /sys to identify the
>>> machine, to make sure we are not lying?
>> There's no such filesystems on BlueGene compute nodes. The CNK kernel
>> redirects I/O call to the I/O node (which runs Linux).
>>
>> I can check that uname reports "CNK" and "BGQ" if you're afraid of
>> people running hwloc/bgq on non-bgq machines.
> My concern is rather than within a few years, new BGQ machines get built
> with a differing architecture. Ideally we would find some
> identifier or version which will for sure change when IBM changes the
> architecture.
>

If a new BlueGene is built, it won't be called Q again, they still have
23 letters to use :)
The BlueGene program has stopped anyway, it was only L, P and Q.

Brice