X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org X-Yahoo-SMTP: jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- Date: Fri, 18 Mar 2011 16:37:06 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: last snapshot (2011-03-13) Message-ID: <20110318203706.GD29306@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20110318174340.11864kumrhjf7ags@messagerie.si.c-s.fr> <20110318180247.GA24890@ednor.casa.cgf.cx> <0B77E7CD-DB7A-4DF0-AA82-FB6EEEDB6EF3@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0B77E7CD-DB7A-4DF0-AA82-FB6EEEDB6EF3@free.fr> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, Mar 18, 2011 at 07:39:39PM +0100, Denis Excoffier wrote: >Le 18 mars 2011 ? 19:02, Christopher Faylor a ?crit : >>Or, are you saying that you still see failures when setting the buffer >>size down to 64K? > >With a buffer 64k all is fine. With a buffer 31*1024*1024, that's >different. It seems that all pipes open at the same time add their >buffers up to an upper limit (the nonpaged value) which cannot be >exceeded. Ok, if I'm reading this right, you're saying that the current snapshot works. I'm looking for verification of that. I understood why the previous snapshot probably wasn't working when I first responded today. We don't need to rehash that. >Now, i suppose that with a 64k buffer, you would not be able to exceed >98Mb/64kb=1568 open pipes at the >same time. Since the allocation of the buffer is now no longer different than previous versions of 1.7.x there shouldn't be any new behavior wrt the memory set aside for pipes. Cygwin should now just work around the potential for seeing ERROR_NO_SYSTEM_RESOURCES when writing large buffers. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple