Cisco Blogs

Hardware Locality 1.2.1 and 1.3rc1 released

August 23, 2011 - 0 Comments

In the vein of awesome software releases (ahem…), Hardware Locality (hwloc) v1.2.1 has been released.  As the “.1” implies, this is a bug fix release of a bunch of little things that crept in the 1.2 series.  A full list of the news-worthy items can be found here.

But more awesome than that is the fact that Hwloc 1.3rc1 has also been released.  The Hwloc 1.3 series brings in some major new features.  The list of new features can be found below.

In the “just because I want to” category, here’s what I want to see: hwloc used in an Android app.  Can anyone think of a legitimate reason — it doesn’t even have to be a good one — to use hwloc in a phone or tablet app?  Yes, I know Android apps are Java and hwloc doesn’t have a Java interface, but someone could kludge one up pretty quickly, right?

  • New feature: Add I/O devices and bridges to the topology using the pciutils library. Only enabled after setting the relevant flag with hwloc_topology_set_flags() before hwloc_topology_load(). See the I/O Devices section in the documentation for details.
  • Discovery: Add associativity to the cache attributes.
  • Discovery: Add support for s390/z11 “books” on Linux.
  • Discovery: Add the HWLOC_GROUPING_ACCURACY environment variable to relax distance-based grouping constraints. See the Environment Variables section in the documentation for details about grouping behavior and configuration.
  • Discovery: Allow user-given distance matrices to remove or replace those discovered by the OS backend.
  • Minor: Add hwloc_obj_add_info to customize object info attributes.
  • Tools: lstopo now displays I/O devices by default. Several options are added to configure the I/O discovery.
  • Tools: hwloc-calc and hwloc-bind now accept I/O devices as input.
  • Tools: Add –restrict option to hwloc-calc and hwloc-distribute.
  • Tools: Add –sep option to change the output field separator in hwloc-calc.
  • Tools: Add –whole-system option to hwloc-ps.

In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.