More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-09-22 Thread Corinna Vinschen
As a follow up on this, I just found that the problem with the Win32 native version of unison described in http://cygwin.com/ml/cygwin/2004-09/msg01131.html is also a consequence of the new pipe code. The hang only happens with the new code, with the old pipe code it works fine. And Karl s

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-09-23 Thread Corinna Vinschen
On Sep 22 20:51, Corinna Vinschen wrote: > As a follow up on this, I just found that the problem with the Win32 > native version of unison described in > > http://cygwin.com/ml/cygwin/2004-09/msg01131.html > > is also a consequence of the new pipe code. The hang only happens > with the new c

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-09-23 Thread Bob Byrnes
On Sep 23, 2:31pm, Corinna Vinschen wrote: -- Subject: Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance > > It seems that NtQueryInformationFile doesn't return useful values > anymore under XP SP2. I'm not quite sure though since it's the first > time I'm looking into this issue.

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-09-23 Thread Corinna Vinschen
On Sep 23 12:28, Bob Byrnes wrote: > OutboundQuota is just the size of the pipe. How do we know that the > cygwin ssh didn't really inherit a huge pipe from the win32-native > unison? We don't unless checking the the source code or the strace, I guess. > The real trouble here seems to be that Wr

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-10-04 Thread Corinna Vinschen
On Sep 23 18:56, Corinna Vinschen wrote: > On Sep 23 12:28, Bob Byrnes wrote: > > OutboundQuota is just the size of the pipe. How do we know that the > > cygwin ssh didn't really inherit a huge pipe from the win32-native > > unison? > > We don't unless checking the the source code or the strace,

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-10-04 Thread Christopher Faylor
On Mon, Oct 04, 2004 at 11:40:10AM +0200, Corinna Vinschen wrote: >On Sep 23 18:56, Corinna Vinschen wrote: >> On Sep 23 12:28, Bob Byrnes wrote: >> > OutboundQuota is just the size of the pipe. How do we know that the >> > cygwin ssh didn't really inherit a huge pipe from the win32-native >> > un

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-10-04 Thread Corinna Vinschen
On Sep 23 12:28, Bob Byrnes wrote: > On Sep 23, 2:31pm, Corinna Vinschen wrote: > -- Subject: Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance > > > > It seems that NtQueryInformationFile doesn't return useful values > > anymore under XP SP2. I'm not quite sure though since it's

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-10-05 Thread Bob Byrnes
I've been working on this, and I think I now understand the underlying problem, but I don't yet have a fix. The problem is that NtQueryInformationFile is stranger than I ever imagined. First, some background, to be sure we're all speaking the same language: Windows pipes actually seem more simila

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-10-05 Thread Christopher Faylor
On Tue, Oct 05, 2004 at 12:26:33PM -0400, Bob Byrnes wrote: >I hope to have more info to report soon. Thanks for the interesting summary of the problem, Bob. cgf

RE: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-10-05 Thread Gary R. Van Sickle
[snip] > But there is a strange twist: When a read is pending on an > empty pipe, then WriteQuotaAvailable is also decremented! I > can't imagine why this would be the case, but it is easy to > demonstrate using a pair of small test programs that I wrote > to experiment with pipe buffering. >

Re: More pipe problems (was Re: [Fwd: 1.5.11-1: sftp performance problem])

2004-10-06 Thread Corinna Vinschen
On Oct 5 12:26, Bob Byrnes wrote: > But there is a strange twist: When a read is pending on an empty pipe, > then WriteQuotaAvailable is also decremented! I can't imagine why this > would be the case, but it is easy to demonstrate using a pair of small > test programs that I wrote to experiment