X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
Message-ID:	<4E347D4B.3070409@gmail.com>
Date:	Sat, 30 Jul 2011 14:53:15 -0700
From:	Daniel Colascione <dan DOT colascione AT gmail DOT com>
User-Agent:	Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Slow performance Win7/64
References:	<loom DOT 20110727T120025-601 AT post DOT gmane DOT org> <j0tc8u$slo$1 AT dough DOT gmane DOT org> <loom DOT 20110729T103121-380 AT post DOT gmane DOT org> <20110729092602 DOT GB19240 AT calimero DOT vinschen DOT de> <loom DOT 20110729T144701-436 AT post DOT gmane DOT org> <20110729130645 DOT GA28223 AT ednor DOT casa DOT cgf DOT cx> <20110730210908 DOT GA31747 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To:	<20110730210908.GA31747@ednor.casa.cgf.cx>
X-IsSubscribed:	yes
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

--------------enig8E7DB138BE0A9A552B18FAF8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 7/30/11 2:09 PM, Christopher Faylor wrote:
> I've checked in a change which uses QueueUserAPC to create threads like
> the signal thread.  As everyone has noted this seems to have a salutory
> effect on the OP's test case.
>=20
> I don't entirely understand why the code which already existed in Cygwin
> to deal with the "slow performance on win7/64" didn't fix the problem but
> using QueueUserAPC seems to solve the problem so I guess won't lose too
> much sleep over this.

I must be missing something: when exactly do we enter an alertable wait sta=
te
that would allow the thread-starting user APC to be delivered? AFAICS, all =
waits
seem to be of the non-alertable variety.


--------------enig8E7DB138BE0A9A552B18FAF8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)

iEYEARECAAYFAk40fU0ACgkQ17c2LVA10VsdxQCguIT6/mhGCiDt1hMyOxPFoAwQ
mZcAoNJJ8HYe2E+FSKyi4R5kHWmTlMbr
=OF8E
-----END PGP SIGNATURE-----

--------------enig8E7DB138BE0A9A552B18FAF8--

- Raw text -