![]() This is different from setting HWLOC_TOPOLOGY_FLAG_INCLUDE_DISALLOWED which gathers all resources but marks the unavailable ones as disallowed.Įnables or disables verbose reporting of errors. Totally ignore administrative restrictions such as Linux Cgroups and consider all resources (PUs and NUMA nodes) as allowed. for performance reason) and it comes with all resources, but the running process is restricted to only a part of the machine (for instance because of Linux Cgroup/Cpuset). This is useful when the topology is not loaded directly from the local machine (e.g. This variable requires the topology to match the current system (see the variable HWLOC_THISSYSTEM). Get the set of allowed resources from the native operating system even if the topology was loaded from XML or synthetic description, as if HWLOC_TOPOLOGY_FLAG_THISSYSTEM_ALLOWED_RESOURCES was set with hwloc_topology_set_flags(). This also enables support for the variable HWLOC_THISSYSTEM_ALLOWED_RESOURCES. This can be used for efficiency reasons to first detect the topology once, save it to a XML file, and quickly reload it later through the XML backend, but still having binding functions actually do bind. This means making the binding functions actually call the OS-specific system calls and really do binding, while the XML backend would otherwise provide empty hooks just returning success. It means that it makes hwloc assume that the selected backend provides the topology for the system on which we are running, even if it is not the OS-specific backend but the XML backend for instance. See also Synthetic topologies.Įnforces the return value of hwloc_topology_is_thissystem(), as if HWLOC_TOPOLOGY_FLAG_IS_THISSYSTEM was set with hwloc_topology_set_flags(). Similarly, enabling verbose messages in the synthetic topology backend can help understand why the description string is invalid. Enabling these verbose messages within hwloc can be useful for understanding failures to parse input XML topologies. hwloc XML backends (see Importing and exporting topologies from/to XML files) can emit some error messages to the error output stream. HWLOC_XML_VERBOSE=1 HWLOC_SYNTHETIC_VERBOSE=1Įnables verbose messages in the XML or synthetic topology backends. For convenience, this backend provides empty binding hooks which just return success. See also Importing and exporting topologies from/to XML files.Įnforces the discovery through a synthetic description string as if hwloc_topology_set_synthetic() had been called. To have hwloc still actually call OS-specific hooks, HWLOC_THISSYSTEM should be set 1 in the environment too, to assert that the loaded file is really the underlying system. This file may have been generated earlier with lstopo file.xml. HWLOC_XMLFILE=/path/to/file.xmlĮnforces the discovery from the given XML file as if hwloc_topology_set_xml() had been called. The behavior of the hwloc library and tools may be tuned thanks to the following environment variables. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |