Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From:	"Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>,
	"cygwin" <cygwin AT cygwin DOT com>
Subject:	RE: MIT shared memory extension
Date:	Fri, 17 May 2002 21:33:10 +0200
Message-ID:	<000101c1fdd9$ad8e4fc0$78a807d5@BRAMSCHE>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
In-Reply-To:	<FC169E059D1A0442A04C40F86D9BA7600C6100@itdomain003.itdomain.net.au>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

> I don't think that the next cygwin release should enable the code. It's
> not ready yet - it's apparently high latency, and needs further work.

but latencies seems to me a generic problem. I remember the lmbench result, for
example context switching
http://sources.redhat.com/ml/cygwin/2002-01/msg01719.html, but unfortunally I
have no idea where to look in the cygwin code and how to detect such bottleneks.
Perhaps there are other people with exactly the needed knowledge, so we can
solve this issue together ?

Ralf





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -