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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=jwlXLVXNOlIq9jzm
	Qw4SmPjXvbP6kNy/lvXZHgeRvcTL1T3nXCbp7FlsdxdOuDw2kgmwBUac3E/PrRMs
	9d6+fpyJ8GlxE8LKjtYnqPa6K2IMBKrDgubyoVQ1gx1TKmp7theu+CgPK29pL8pK
	NqwUo2kFoQ8yJbf6nNes6d48r+w=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=QiltaLGijxn6VoZNxG8xCa
	4YanM=; b=fk/lgwWeOCRYSKx4Z9YX4mqWiAN2Xeo9u8F//HXwtUa8JZGQaAz4vU
	+ZSZDA5a+SZ1Hq+0NM7zrnDARZjWFXXBsyVk+EUtQ6NZ0FeLh3VJnQU6wUSD/cg1
	gbXhPNt+JAgmbBTbPnBgdeHSp2hXS2wLWXqmmTCK5a7lyAb8nMMlI=
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=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=UD:t, Canada, H*Ad:D*ca, inglis
X-HELO:	smtp-out-so.shaw.ca
X-Authority-Analysis:	v=2.3 cv=OeS28CbY c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=QyXUC8HyAAAA:8 a=B6mlKY4akW7_WWLOp5UA:9 a=QEXdDO2ut3YA:10
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: More oddities with multiple processor groups
To:	cygwin AT cygwin DOT com
References:	<87in8xwre7 DOT fsf AT Rainer DOT invalid>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID:	<b21ad6c9-dadf-6ba2-251a-f374c8fcb89a@SystematicSw.ab.ca>
Date:	Fri, 13 Apr 2018 11:22:29 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version:	1.0
In-Reply-To:	<87in8xwre7.fsf@Rainer.invalid>
X-CMAE-Envelope:	MS4wfFTclRBl7hS/1kZbSKL2NHMUFmCcthjwN27qEhMlCnK68rIIRzpFdKFBmLJ50ip82H0DmVlv/mViknfrMhM5TXx3rRkImDnMuGIQFlpUSHn0O+lSbDfY X0Tj/8EaQGfIvoTLRVw4j5hLKel0ZX20MjULrZNLOVkFcUh2FOubePo+U4kRIqZDceRsaaGxqtG3/Q==
X-IsSubscribed:	yes

On 2018-04-11 12:05, Achim Gratz wrote:
> I seem to be the first to try Cygwin on a box that has multiple
> processor groups, which seems odd.  Anyway, I've already noticed two
> more things that indicate that Cygwin and/or Cygwin applications
> currently don't deal well with the situation:
> 
> 1. Trying to run top, it shows only the first 16 processors and then
> exits with an error that "openproc failed".  Interestingly enough it
> will keep running despite this error when running under strace (still
> only showing the processors from one group, presumably the one that top
> got started in).
> 
> 2. Git will correctly determine that it can use 32 threads for garbage
> collection, but it starts them all in the same processor group.
> 
> 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.
> 
> 
> Some more info on these differences (and already a bit outdated
> w.r.t. the way processor groups are formed):
> 
> https://software.intel.com/en-us/blogs/2010/12/16/tbb-30-high-end-many-cores-and-windows-processor-groups
> 
> If it would be possible for Cygwin to hide that ugliness from Cygwin
> applications I think that'd be highly welcome.  Otherwise there might
> need to be some option to restrict Cygwin to a single processor group
> for some applications to work (correctly).

Have you tried installing and running hwloc package to find out how it sees your
system?
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.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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 -