From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: posix thread scaling issue
Date: Sat, 2 Sep 2023 21:13:13 -0700 [thread overview]
Message-ID: <0dd30adc-9cc1-1440-edb2-c8efa5904fcb@maxrnd.com> (raw)
In-Reply-To: <1a894e01-0dee-7a14-d94a-40034b88275f@maxrnd.com>
Sorry, I mis-spoke in my previous post...
Mark Geisert via Cygwin wrote:
> Briefly, you can't move a thread
> outside the processor group it's currently in; you have to move its process to the
> new group first.
That's backward. You can't add a process to multiple processor groups or move it
from one group to another. You can, however, move a process's threads one-by-one
to a different processor group.
I'm now recalling how hair-pulling it was to get this correct when coding it.
Cheers,
..mark
next prev parent reply other threads:[~2023-09-03 4:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 14:57 jeff
2023-09-02 17:56 ` Brian Inglis
2023-09-02 18:27 ` jeff
2023-09-02 19:59 ` Brian Inglis
2023-09-02 20:04 ` jeff
2023-09-03 6:13 ` ASSI
2023-09-03 3:50 ` Mark Geisert
2023-09-03 4:13 ` Mark Geisert [this message]
2023-09-02 19:30 André Bleau
[not found] ` <e36d50d5-75d0-40d5-92e2-02d04092fd77@jeffunit.com>
2023-09-02 21:23 ` André Bleau
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0dd30adc-9cc1-1440-edb2-c8efa5904fcb@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).