public inbox for
 help / color / mirror / Atom feed
From: Achim Gratz <>
Subject: Re: More oddities with multiple processor groups
Date: Fri, 13 Apr 2018 19:55:00 -0000	[thread overview]
Message-ID: <87lgdq51b4.fsf@Rainer.invalid> (raw)
In-Reply-To: <> (Brian	Inglis's message of "Fri, 13 Apr 2018 11:22:29 -0600")

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 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:
Unsubscribe info:

      reply	other threads:[~2018-04-13 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 18:05 Achim Gratz
2018-04-13 14:12 ` L A Walsh
2018-04-13 18:29   ` Brian Inglis
2018-04-13 19:17     ` Corinna Vinschen
2018-04-13 17:22 ` Brian Inglis
2018-04-13 19:55   ` Achim Gratz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lgdq51b4.fsf@Rainer.invalid \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).