As a side note, does anyone know how if at all power states in the system would be affected differently between a normal priority thread that sleeps versus a low priority thread that runs all of the time?
Sent from Surface Pro
From: xxxxx@resplendence.com
Sent: Friday, July 03, 2015 2:45 PM
To: Windows File Systems Devs Interest List
You can lower the priority of your threads. It will not allow you to control
CPU consumption but you will be less invasive in case there is competition,
if that is useful depends on what you really want.
That is the obvious reply - do you know it to be true or just suppose that no additional sophistication exists?
I don’t know; hence the question. I do know that under specific circumstances, a single thread cannot cause full turbo-boot when all of the other cores are idle. I don’t know how it is implemented, but I have observed the behaviour
Sent from Surface Pro
From: xxxxx@resplendence.com
Sent: Friday, July 03, 2015 7:30 PM
To: Windows File Systems Devs Interest List
As a side note, does anyone know how if at all power states in the system would be affected differently >between a normal priority thread that sleeps versus a low priority thread that runs all of the time?
A low priority thread that runs all the time will still run all the time if there is no competition so it will not allow the processor on which it’s running to go into a sleep state. A thread that calls sleep allows the processor to go into a power saving state if there are no other threads to be scheduled on that processor.