Multiple numa support

[muratyurdakul75]

More than one NUMA should be supported.

Especially in server systems, there are 2 NUMA. But WSL only uses 1 of them. And the maximum 64 processor limit should be increased.

Especially there are servers that only run WSL. And all resources are used for WSL. But since there is only one NUMA support, half of the CPU resources are wasted. Having 2 NUMA support would be very good for performance. For those who want to use single NUMA, settings can be made from the .wslconfig file.

[github-actions[bot]]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[github-actions[bot]]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

``` .wslconfig found Detected appx version: 2.2.4.0 Found no WSL traces in the logs ```

[github-actions[bot]]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

``` .wslconfig found Detected appx version: 2.2.4.0 Found no WSL traces in the logs ```

[github-actions[bot]]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

``` Found '/feature', adding tag 'feature' .wslconfig found Detected appx version: 2.2.4.0 Found no WSL traces in the logs ```

[VajdikA]

Hi @muratyurdakul75 I see that you want more than 64 threads in Pi Node. I have 2 NUMA 16/32, 64T in total, so the WSL2 fix was not needed yet. My another server with more than 64T is on the way, but I already work on resolving this for >64T. Try this and let me know your result https://github.com/xieyubo/WSL2

[muratyurdakul75]

WslLogs-2024-09-18_18-05-19.zip

[github-actions[bot]]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

``` .wslconfig found Detected appx version: 2.2.4.0 Found no WSL traces in the logs ```

[muratyurdakul75]

/emailed-logs

[github-actions[bot]]

Diagnostic information

``` Found '/emailed-logs', adding tag 'emailed-logs' ```