Mail Archives: cygwin/2007/06/07/13:42:15
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/
- Raw text -