X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 12 Jan 2011 15:59:26 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: /proc/meminfo capped at 4GB Message-ID: <20110112205926.GA29400@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, Jan 12, 2011 at 12:51:05PM -0800, Daniel Colascione wrote: >I recently upgraded my main workstation to 16GB of memory. Although >native Windows tools display the expected values, the figures in >Cygwin's /proc/meminfo seem capped at 4GB. Is this behavior by design? >Is it just due to WOW64? > >e.g., >Mem: 4294967295 0 4294967295 >Swap: 4227117056 0 4227117056 Cygwin is a 32-bit DLL. 0xffffffff = 4294967295 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