Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Fri, 22 Nov 2002 23:04:15 +0100
From: thomas <tom@huno.net>
Reply-To: thomas <cygwin@cygwin.com>
X-Priority: 3 (Normal)
Message-ID: <19719277625.20021122230415@huno.net>
To: Christopher Faylor <cygwin@cygwin.com>
Subject: Re: pipe performance problem
In-Reply-To: <20021122210856.GA10679@redhat.com>
References: <777770015.20021122040845@huno.net>
 <007301c291ff$eb9ce050$78d96f83@pomello> <21545718.20021122114035@huno.net>
 <12415481703.20021122220059@huno.net> <20021122210856.GA10679@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Christopher Faylor <cgf@redhat.com> wrote:

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

from a quick look i found /dev/piper and things like that in tty.cc and
since thats what the strace logs are also showing i thought tty.cc is
relevant.
now please correct me if i'm wrong, but when it works with 1.1.18 and
not with 1.3.x and the only constant that changes is cygwin, wouldn't
every fan of logic scream out loud then: it's cygwin! :)

anyway i'll try to provide more information and will do some additional
testing. and i'll write the cdrecord developer about my new findings and
see what he thinks about it.

thomas


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

