Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.7.2rc1r5763
Start time: Tue Aug 27 21:05:33 EDT 2013
End time: Tue Aug 27 21:09:42 EDT 2013
Your friendly daemon,
Cyrador
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.8a1r5764
Start time: Tue Aug 27 21:01:01 EDT 2013
End time: Tue Aug 27 21:05:33 EDT 2013
Your friendly daemon,
Cyrador
Le 27/08/2013 18:15, Jiri Hladky a écrit :
> using the weights looks like a good solution to me. However, we need
> to think if and how we should propagate the weight via the upper
> levels of the hierarchy. So for example if you have a socket with 4
> cores and cores 0&1 and 2&3 share L2 cache
The problem I have while playing with this is that it takes a lot of
space. Putting the entire uname on a single line will be truncated when
the topology drawing isn't large (on machines with 2 cores for
instance). And using multiple lines would make the legend huge.
We could make it optional. But
Hi Brice,
hi Chris,
using the weights looks like a good solution to me. However, we need to
think if and how we should propagate the weight via the upper levels of the
hierarchy. So for example if you have a socket with 4 cores and cores 0&1
and 2&3 share L2 cache than the question is if and how
Le 27/08/2013 05:07, Christopher Samuel a écrit :
> On 27/08/13 00:07, Brice Goglin wrote:
>
> > But there's a more general problem here, some people may want
> > something similar for other cases. I need to think about it.
>
> Something like a sort order perhaps, combined with some method to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/08/13 00:07, Brice Goglin wrote:
> But there's a more general problem here, some people may want
> something similar for other cases. I need to think about it.
Something like a sort order perhaps, combined with some method to
exclude or weight
