search

Gwinel / likwid

Automatically exported from code.google.com/p/likwid
GNU General Public License v3.0
0 stars 0 forks source link

likwid does not work in a restricted CPUSET #63

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
If likwid is invoked inside a restricted Linux CPUSET it may not work correctly 
or quit with an error.

This situation can occur in shared environments if the batch scheduler imposes 
a cpuset on a job.

Original issue reported on code.google.com by jan.trei...@gmail.com on 30 Sep 2012 at 1:55

GoogleCodeExporter commented 9 years ago 
Possible solution:

As an alternative to cpuid extract information from /proc/cpuinfo (apicID).
Need still to ad proper error handling if non allowed processors are requested.

Original comment by jan.trei...@gmail.com on 30 Sep 2012 at 1:58

GoogleCodeExporter commented 9 years ago 
Decided on the following solution:

There is an additional small application which will extract the topology 
information and store it to a file. On startup all likwid apps will check if 
this file is there and pick up the topology info, if it is missing it will be 
extracted as it happens now.

Original comment by jan.trei...@gmail.com on 30 Aug 2013 at 8:19

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision fd794b77c2f5.

Original comment by jan.trei...@gmail.com on 12 Sep 2013 at 11:19