-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to "escape" the system-wide CPU set? #15
Comments
Hi Fredrik, |
@zodiacon Any updates on reproducing this issue? |
Sorry, I've been super busy with work and other stuff and didn't get around to it yet. |
Gentle reminder. |
Really sorry for the crazy delay... |
It also seems that at some point the system CPU set is reset, need further testing to understand why. |
I've also experienced the same behavior, which really puzzled me. |
Status update: Microsoft have published How to set up a Device for Real-Time Performance |
Thank you for this. |
@forderud Have you successfully run an application on a dedicated CPU? |
I just tested on a Windows 11 Pro 21H2, and SoftRT seemed to work fine there. Just follow the instructions on https://learn.microsoft.com/en-us/windows/iot/iot-enterprise/soft-real-time/soft-real-time-device#use-mdm-bridge-wmi-provider-to-configure-the-windowsiot-csp if you want to test yourself. I recommend testing in a VM, since it's difficult (and possibly impossible) to disable the feature after being enabled. |
I'll try it. Thanks! |
The feature can be reverted by deleting the |
Thanks a lot for informing about the I've added a note of the registry key in a Document how to disable Soft-RT enhancement request to Microsoft that I've previously opened. |
Thanks for a great book Pavel, and for sharing code samples. I'm interested in using CPU Sets to dedicate certain CPU cores to real-time signal processing tasks.
I've played a bit with CpuSet.exe based on the instructions in Windows Internals 7th ed. Part 1, and have successfully managed to change the system-wide CPU set. Changing the CPU set for a given process also works, but only within the system-wide CPU set. This means that I'm not able to reproduce "EXPERIMENT: CPU sets" in the book where CPU 0 is dedicated to the CPUSTRESS process.
Any advise on how to configure a process to "escape" the system-wide CPU set, so that it can get dedicated CPU cores?
Not sure if it's relevant, but I'm running Win10 Pro version 1903 (64bit) build 18362.267.
The text was updated successfully, but these errors were encountered: