| | 58 | |
| | 59 | It's not clear how (or even whether Windows) lets you specify the processor group |
| | 60 | for a process, new or existing. |
| | 61 | |
| | 62 | This looks like it might work: |
| | 63 | |
| | 64 | https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-setprocessaffinitymask |
| | 65 | |
| | 66 | One of the above docs says "The operating system initially assigns each process to |
| | 67 | a single group in a round-robin manner across the groups in the system." |
| | 68 | Does that mean there's no control in process creation? |
| | 69 | |
| | 70 | If processor group/affinity is inherited, |
| | 71 | maybe the client can changes its group prior to creating the process? |
| | 72 | |
| | 73 | Can we create and use an "startup info" structure during process creation? |
| | 74 | |
| | 75 | https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-initializeprocthreadattributelist |
| | 76 | |
| | 77 | https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-updateprocthreadattribute |
| | 78 | |
| | 79 | https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createprocessasusera |
| | 80 | |
| | 81 | |