Hi all, I noticed that POCL (on ec8598d) always seems to use all cores on my machine, regardless of whether a subDevice has been set up. Following this I created a simple test script (attached, core_check.py) that varies both the number of cores supplied to clCreateSubDevices, as well as the desired platform (comparing against a reference Intel 16.1.1 CPU implementation).
The results seem to imply that indeed, POCL doesn't respect the number of cores (compute units) passed in to clCreateSubDevices with type CL_DEVICE_PARTITION_BY_COUNTS: platform: pocl num cores: 1 elapsed time: 2.774392e+03 platform: pocl num cores: 2 elapsed time: 2.484821e+03 platform: pocl num cores: 4 elapsed time: 2.598454e+03 platform: pocl num cores: 8 elapsed time: 2.532769e+03 platform: pocl num cores: 16 elapsed time: 2.540196e+03 platform: Intel num cores: 1 elapsed time: 2.027040e+03 platform: Intel num cores: 2 elapsed time: 1.169391e+03 platform: Intel num cores: 4 elapsed time: 7.340540e+02 platform: Intel num cores: 8 elapsed time: 6.832930e+02 platform: Intel num cores: 16 elapsed time: 5.666650e+02 However, clCreateSubDevices *is* implemented in on the github repo (I believe, https://github.com/pocl/pocl/blob/a221e5b33efd89b3165f59cf15e67487e5a31076/lib/CL/clCreateSubDevices.c#L38) nor can I spot anything obviously wrong with it. Is this desired behavior? Or a bug? Thanks Nick
fission_check.tar.gz
Description: GNU Zip compressed data
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
