DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=W2ah4Xf8njQ66fY1ZxK20gUOJkFpIJnpC9j/Kd6z0eHm6s/u6nnAn
	oCqkkxFkEVzAUfXN3VdSAf4lh4h7ToN7aTmpiwC9RaA+FR2j6zZObBxOEPA4GCPf
	mcakdDonBZew0p/x08z3UJP1C593oWIL6MB5V2JjaeC7jnm/5V10M4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Fri, 13 Apr 2018 21:17:34 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: More oddities with multiple processor groups
Message-ID: <20180413191734.GC27440@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <87in8xwre7 DOT fsf AT Rainer DOT invalid> <5AD0BAE5 DOT 2040904 AT tlinx DOT org> <8829ca51-a131-a88b-4b36-00c965af0b2b AT SystematicSw DOT ab DOT ca>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="i7F3eY7HS/tUJxUd"
Content-Disposition: inline
In-Reply-To: <8829ca51-a131-a88b-4b36-00c965af0b2b@SystematicSw.ab.ca>
User-Agent: Mutt/1.9.2 (2017-12-15)

--i7F3eY7HS/tUJxUd
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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=20
> >> use any of the advertised logical processors from a single application=
,=20
> >> while on Windows you need to first create a thread and set it's affini=
ty to
> >> a different group than where your process was started in, then assign =
each
> >> new thread an affinity to one of the available groups.  If you don't do
> >> that, all threads will be restricted to the original group.
> > Not exactly true.  They are not *restricted* -- it's a *feature* of the
> > Windows scheduler, in that future procs/threads inherit the cpu of the
> > parent.  Linux's scheduler is more advanced as well as being replaceabl=
e.  MS
> > doesn't want you to do that
> >> there might need to be some option to restrict Cygwin to a single proc=
essor
> >> group for some applications to work (correctly).
> > There is.  Start them all on a single cpu & set the cpu mask.  Pretty m=
uch=20
> > the same way you restrict procs on linux -- you can run them with a spe=
cific
> > cpu mask, and most programs will keep running w/that mask.
> > Unfortunately, AFAIK, I don't think POSIX specifies a way to set affini=
ties,
> > so I'm not sure how cygwin would do it.
>=20
> Glibc adds {pthread,sched}_...affinity... functions.
> Linux uses namespaces, control groups (cgroups), cpusets, sysfs/kernfs:

We would only be able to support it partially.  Windows doesn't
allow to set thread affinity across CPU groups.  There's no simple
function to set process CPU group affinity, only a function to set
process affinity within a single group.  And it has a restriction
in that all current threads have to run in the same CPU group.
The API is pretty tricky.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--i7F3eY7HS/tUJxUd
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlrRAk4ACgkQ9TYGna5E
T6CWMBAAnqSIvEnwfXVBExWSjNNz+Qddbbr5Qd3mY6NP2cBoTzNkKXv39okGrZxQ
Of8CJ3Ipej2iWP6MloUy4BUWu0FNGgdcfYppRYVdgLaDrEQmSB8ED3Cdth0fdSgX
5CE6m2sA7T0aMeUyL/Z1+o27s8WxwUDILHXwT5w5I2nuPEi02Tgn8wDDffe9HTGm
h17NBCbpX5gHv7hDJCte3O11CzwyH+n8DDjE7cr0MFMCfUB5uJLtmNe5J5a8CA9D
dpsuVJHubCjxQJ222QV8BUBkWK6jNRyrLTp9tK0tLWYowtIm1aw0nA2kD17k1pNU
XFoRhBHKOrABJXwFu3sFAj9F3QDQD1TUG3Ta7r1C0JhPtzzgssYwfBQbsJmEYbaG
YRM3Mb9rjK/YwZGAoTf5xIhzhA0+VGc2RkaHjzktyN3mkrNaUIlUykZumx+4VSBY
3n0ZP1VESmkgkYy0r4lvf9qPKi7eZ0oAsXh6jCqI9hETr/Q9keQL7o0Z12jeftoF
iktyY65MBU1up/I0OFI5O+C5OWApJ2bgEXVvrj6PI4wPG580xRVrNZWw9f7GcK1v
gTvIJtDzwZpnHkbJDehb2xwOAc8FYKTBOgKcBzFrynOe4QbaiS3JUu+PV0Hr+KW1
FXw7VxYsZf1MrCQ7vDwrQcIhEKTxnTfgwSqMboBiUKXGrj1bIrA=
=5wEG
-----END PGP SIGNATURE-----

--i7F3eY7HS/tUJxUd--