|Value returned by hwloc_compare_types() when types can not be compared.|
Type of one side (upstream or downstream) of an I/O bridge.
|Host-side of a bridge, only possible upstream.|
|PCI-side of a bridge.|
|Instruction cache. Only used when the HWLOC_TOPOLOGY_FLAG_ICACHES topology flag is set.|
Type of a OS device.
|Operating system block device. For instance sda on Linux.|
|Operating system GPU device. For instance :0.0 for a GL display, card0 for a Linux DRM device.|
|Operating system network device. For instance the eth0 interface on Linux.|
|Operating system openfabrics device. For instance the mlx4_0 InfiniBand HCA device on Linux.|
|Operating system dma engine device. For instance the dma0chan0 DMA channel on Linux.|
|Operating system co-processor device. For instance mic0 for a Xeon Phi (MIC) on Linux, opencl0d0 for a OpenCL device, cuda0 for a CUDA device.|
Type of topology object.
Do not rely on the ordering or completeness of the values as new ones may be defined in the future! If you need to compare types, use hwloc_compare_types() instead.
|Whole system (may be a cluster of machines). The whole system that is accessible to hwloc. That may comprise several machines in SSI systems like Kerrighed.|
|Machine. The typical root object type. A set of processors and memory with cache coherency.|
|NUMA node. A set of processors around memory which the processors can directly access.|
|Physical package, what goes into a socket. In the physical meaning, i.e. that you can add or remove physically.|
|Cache. Can be L1i, L1d, L2, L3, ...|
|Core. A computation unit (may be shared by several logical processors).|
|Processing Unit, or (Logical) Processor. An execution unit (may share a core with some other logical processors, e.g. in the case of an SMT core). Objects of this kind are always reported and can thus be used as fallback when others are not.|
|Group objects. Objects which do not fit in the above but are detected by hwloc and are useful to take into account for affinity. For instance, some operating systems expose their arbitrary processors aggregation this way. And hwloc may insert such objects to group NUMA nodes according to their distances. These objects are ignored when they do not bring any structure.|
|Miscellaneous objects. Objects without particular meaning, that can e.g. be added by the application for its own use, or by hwloc for miscellaneous objects such as MemoryModule (DIMMs).|
|Bridge. Any bridge that connects the host or an I/O bus, to another I/O bus. Bridge objects have neither CPU sets nor node sets. They are not added to the topology unless I/O discovery is enabled with hwloc_topology_set_flags().|
|PCI device. These objects have neither CPU sets nor node sets. They are not added to the topology unless I/O discovery is enabled with hwloc_topology_set_flags().|
|Operating system device. These objects have neither CPU sets nor node sets. They are not added to the topology unless I/O discovery is enabled with hwloc_topology_set_flags().|
Compare the depth of two object types. Types shouldnt be compared as they are, since newer ones may be added in the future. This function returns less than, equal to, or greater than zero respectively if type1 objects usually include type2 objects, are the same as type2 objects, or are included in type2 objects. If the types can not be compared (because neither is usually contained in the other), HWLOC_TYPE_UNORDERED is returned. Object types containing CPUs can always be compared (usually, a system contains machines which contain nodes which contain packages which contain caches, which contain cores, which contain processors).
Note:HWLOC_OBJ_PU will always be the deepest.
This does not mean that the actual topology will respect that order: e.g. as of today cores may also contain caches, and packages may also contain nodes. This is thus just to be seen as a fallback comparison method.
Generated automatically by Doxygen for Hardware Locality (hwloc) from the source code.
|Version 1.11.1||HWLOCALITY_OBJECT_TYPES (3)||Thu Oct 15 2015|