This is the mail archive of the
mailing list for the Cygwin project.
Re: More oddities with multiple processor groups
Brian Inglis writes:
> Have you tried installing and running hwloc package to find out how it sees your
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 to processor group aware state by
default then my understanding is that at least the processor group would
have to be explicitly selected for each thread, while on Linux the
scheduler would eventually use all of the NUMA nodes unless the
application tells it prefers different affinities.
> If you run lstopo under X, you get a pretty diagram, but you can also run
> lstopo-no-graphics aka hwloc-ls without X. Running "apropos hwloc" lists
> commands you can use to manipulate the topology.
I'll have that machine switched to "flat mode" which will result in a
single processor group (still with two NUMA nodes, so things like MPI
still know what to do). I have no actual use for the current topology
and don't want to deal with the obvious complications, especially as I
seem to be the only person who'd have them. If I can free up some time
I will want to find out why top crashes, but for me that'l be the end of
it if I even get that far.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple