X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=D5mmUCXA1M1gLthmlDCirLhxLXpLMJmsNGahEVFU0yJ
	bXI6CaWBTnJ098m3rmiF5S/zA8L1wohgg2CEzHMq44239qPN/6zVsTFFlm/SQcju
	ns2zPoHE+hccUDEvcTPqspyUWyqJWw3DleFuf6kwvqCE2XWalOgE++/x2WAkyzzw
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=1z5I09SbKi0gaEvol+IIPWXPlkE=; b=JbtnasNLoxsGJV+UX
	PHqCngtF+CWr73njEJarFIOpA9I7me2FIktRUNdNyNQ6+X3vmY2Jmx8vGOUBG1bG
	A7vq3/sT8dQ0Xmm8fsADHGDVmcI9jln//6lwlC4oH0ME/S+Jl+iTLSRd9IwlkKYO
	9oBcWOOI09iC3yKheaPH1x+Qkg=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-6.9 required=5.0 tests=BAYES_00,GIT_PATCH_2 autolearn=ham version=3.3.2 spammy=advertised
X-HELO:	Ishtar.sc.tlinx.org
Message-ID:	<5AD0BAE5.2040904@tlinx.org>
Date:	Fri, 13 Apr 2018 07:12:53 -0700
From:	L A Walsh <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: More oddities with multiple processor groups
References:	<87in8xwre7 DOT fsf AT Rainer DOT invalid>
In-Reply-To:	<87in8xwre7.fsf@Rainer.invalid>
X-IsSubscribed:	yes

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, 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 replaceable.  MS doesn't want you to do that

> there might
> need to be some option to restrict Cygwin to a single processor group
> for some applications to work (correctly).
---
	There is.  Start them all on a single cpu & set the cpu 
mask.  Pretty much the same way you restrict procs on linux --
you can run them with a specific cpu mask, and most programs will
keep running w/that mask.

	Unfortunately, AFAIK, I don't think POSIX specifies
a way to set affinities, so I'm not sure how cygwin would do it.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -