Message-ID: <20110318174340.11864kumrhjf7ags@messagerie.si.c-s.fr>
Date: Fri, 18 Mar 2011 17:43:40 +0100
From: EXCOFFIER Denis <denis.excoffier@c-s.fr>
To: cygwin@cygwin.com
Subject: last snapshot (2011-03-13)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.5)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

This follows http://cygwin.com/ml/cygwin/2011-03/msg00563.html

> Maybe it has something to do with the nonpaged pool size?  MSDN states:
>
>  "Every time a named pipe is created, the system creates the inbound
>   and/or outbound buffers using nonpaged pool, which is the physical
>   memory used by the kernel.  [...]
>   The input and output buffer sizes are advisory. The actual buffer
>   size reserved for each end of the named pipe is either the system
>   default, the system minimum or maximum, or the specified size rounded
>   up to the next allocation boundary. The buffer size specified should
>   be small enough that your process will not run out of nonpaged pool,
>   but large enough to accommodate typical requests."

We could be in the right direction: i've open "Task manager" on both
machines and the non-failing one has "Nonpaged=98Mb" and the
failing one has "Nonpaged=36Mb" (only). Of course, these values are
constantly moving, but seem to remain within an interval of a few Mb.

Denis Excoffier.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


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