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
Date: Fri, 22 Nov 2002 16:08:56 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: pipe performance problem
Message-ID: <20021122210856.GA10679@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <777770015 DOT 20021122040845 AT huno DOT net> <007301c291ff$eb9ce050$78d96f83 AT pomello> <21545718 DOT 20021122114035 AT huno DOT net> <12415481703 DOT 20021122220059 AT huno DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12415481703.20021122220059@huno.net>
User-Agent: Mutt/1.5.1i

On Fri, Nov 22, 2002 at 10:00:59PM +0100, thomas wrote:
>well i'm a bit lost here.  can someone point me in some direction what
>to do next?  where is the relevant code, i figured it must be pipe.cc
>and tty.cc or is there some other place?

If the relevant code was obvious then it would be trivial to fix.  I'm
not even convinced that there is a cygwin problem here.  It doesn't
appear to be doing anything wrong.  However, unless you are doing something
with ttys I don't see why that's appropriate.

>also do i have to recompile the binaries when i build a new cygwin1.dll
>to test the changes?

If you take this to the logical conclusion it would mean that every time
we released a new version of the cygwin DLL we'd have to regenerate every
cygwin package.  So, no, you don't rebuild binaries to test cygwin DLL
changes.

cgf

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