> 在 2020/1/6 17:27, Malcolm MacLeod 写道: > > Hello, > > > > ... > > > > It seems to me that it should not be difficult to create similar wrappers > > (for > > SetThreadGroupAffinity) that wrap the appropriate win32 calls (as the above > > linked code wraps > > SetProcessAffinityMask) such that my program (and other peoples programs) > > can then set the processor > > groups as required to fully utilise all cores on high core count systems. > > > > > > Before I spend time writing such a wrapper I wanted to get opinions - would > > the project accept a > > patch/pull request that adds a wrapper such as this? Is there some other > > way people would prefer to > > tackle the problem? > > > > It's probably not our goal to provide such wrappers, because we are less > likely to maintain them. We take WinSDK as references (we provide what > they provide - headers, libraries, tools, etc.). We take Glibc as > references (we provide many POSIX-conforming functions as well as _some_ > of GNU extensions such `getopt_long()` and the 10-byte `long double`). > We take Wine as references too (we even share some headers with them). > Something without a reference is unlikely to be accepted unless it is > proved to be very essential. >
Would you not deem actually being able to use more than half the cores on a high core count machine as 'essential'? It seems like a pretty bad limitation to me, granted not every application needs this sort of performance but there are certainly lots that do and its only going to get more common. The windows people don't seem to be about to do away with this limitation in the near future, and machines with more core availability are only getting more and more common. So if not a wrapper then what/how would you suggest that people who need their programs to support this deal with it? _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
