X-Spam-Check-By: sourceware.org
Message-ID: <ba40711f0706071041u66e12b81k23639ee67332df49@mail.gmail.com>
Date: Thu, 7 Jun 2007 13:41:44 -0400
From: "Lev Bishop" <lev DOT bishop AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New package: brltty 3.8
In-Reply-To: <20070607164933.GF4110@implementation>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Disposition: inline
References: <announce DOT 20070605230831 DOT GC3356 AT implementation> 	 <20070606085100 DOT GA5082 AT implementation> <4666819A DOT 52A6488D AT dessent DOT net> 	 <20070606192445 DOT GG6500 AT implementation> 	 <20070606201111 DOT GA2366 AT ednor DOT casa1 DOT cgf DOT cx> 	 <20070607114950 DOT GA3958 AT implementation> 	 <20070607122642 DOT GA31803 AT trixie DOT casa DOT cgf DOT cx> 	 <20070607160859 DOT GA3577 AT implementation> 	 <20070607163744 DOT GA4972 AT ednor DOT casa1 DOT cgf DOT cx> 	 <20070607164933 DOT GF4110 AT implementation>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l57Hg32x019029

On 6/7/07, Samuel Thibault wrote:
> Christopher Faylor, le Thu 07 Jun 2007 12:37:44 -0400, a écrit :
> > On Fri, Jun 08, 2007 at 12:08:59AM +0800, Samuel Thibault wrote:
> > >To the best of my knowledge, there is no "unixish" way in cygwin
> > >to access these pipes, so we just used CreateNamedPipe().
> >
> > So don't use named pipes.
>
> What instead?  Just TCP/IP? (it's quite sluggish).

Maybe TCP/IP is not the most efficient way to send data to the local
machine, but nevertheless, we're talking about sending (braille) text
here aren't we? A cygwin loopback ttcp connexion on my laptop gets...
bash-3.2$ ttcp -fM -sr &  ttcp -fM -n80000 -st 127.0.0.1
[1] 3000
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp
ttcp-r: socket
ttcp-t: buflen=8192, nbuf=80000, align=16384/0, port=5001  tcp  -> 127.0.0.1
ttcp-t: socket
ttcp-r: accept from 127.0.0.1
ttcp-t: connect
ttcp-t: 655360000 bytes in 8.00 real seconds = 78.12 MB/sec +++
ttcp-t: 80000 I/O calls, msec/call = 0.10, calls/sec = 10000.00
ttcp-t: 0.6user 5.6sys 0:08real 78%
ttcp-r: 655360000 bytes in 8.00 real seconds = 78.12 MB/sec +++
ttcp-r: 86662 I/O calls, msec/call = 0.09, calls/sec = 10832.75
ttcp-r: 0.8user 3.1sys 0:08real 49%
bash-3.2$
[1]+  Done                    ttcp -fM -sr
...around 80MByte/sec, which maybe isn't as fast as it could be using
native functionality, but surely brltty doesn't need *that* much
bandwidth for transferring text?

Lev

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/