Hi Jeff, On Mon, 29 Oct 2018 at 20:04, Jeff Furlong <jeff.furlong@xxxxxxx> wrote: > > Hi All, > Back in http://git.kernel.dk/cgit/fio/commit/?id=c479640d6208236744f0562b1e79535eec290e2b several updates were made for Windows CPU affinity. However, using the cpus_allowed since fio 3.6 and latest git appears to throw error messages. Consider a job: > > fio --name=test --ioengine=windowsaio --direct=1 --rw=write --overwrite=1 --filename=\\.\PHYSICALDRIVE1 --runtime=1s --thread --cpus_allowed=0-1 --cpus_allowed_policy=shared > > fio_setaffinity: failed to set thread affinity (pid 2768, group 0, mask 10000, GetLastError=87) > fio_setaffinity: failed to set thread affinity (pid 2372, group 0, mask 20000, GetLastError=87) > clock setaffinity failed: No error > > It seems err 87 is ERROR_INVALID_PARAMETER, but any idea why "GROUP_AFFINITY struct's Reserved members are not initialised to 0?" Might it be related to Windows version? Seems to fail on 2012 and 2016. Thanks. Which version of fio are you compiling with, which cpus do you have and what is the output when you use --debug=process in fio line? -- Sitsofe | http://sucs.org/~sits/
