Brian Inglis writes:
> Have you tried installing and running hwloc package to find out how it sees
> your
> system?
Yes. That is OK, but it doesn't change the fact that an application in
Cygwin can see N processors, but then can't actually run on all of them.
If Cygwin would switch the process t
On Apr 13 12:29, Brian Inglis wrote:
> On 2018-04-13 08:12, L A Walsh wrote:
> > Achim Gratz wrote:
> >> The problem here is that on Linux you don't need to do anything extra to
> >> use any of the advertised logical processors from a single application,
> >> while on Windows you need to first cr
On 2018-04-13 08:12, L A Walsh wrote:
> Achim Gratz wrote:
>> The problem here is that on Linux you don't need to do anything extra to
>> use any of the advertised logical processors from a single application,
>> while on Windows you need to first create a thread and set it's affinity to
>> a dif
On 2018-04-11 12:05, Achim Gratz wrote:
> I seem to be the first to try Cygwin on a box that has multiple
> processor groups, which seems odd. Anyway, I've already noticed two
> more things that indicate that Cygwin and/or Cygwin applications
> currently don't deal well with the situation:
>
> 1.
Achim Gratz wrote:
The problem here is that on Linux you don't need to do anything extra to
use any of the advertised logical processors from a single application,
while on Windows you need to first create a thread and set it's affinity
to a different group than where your process was started in,
I seem to be the first to try Cygwin on a box that has multiple
processor groups, which seems odd. Anyway, I've already noticed two
more things that indicate that Cygwin and/or Cygwin applications
currently don't deal well with the situation:
1. Trying to run top, it shows only the first 16 proc
6 matches
Mail list logo
