From: One Angry User <angry@lusers.org>
To: The Cygwin-Talk Malingering List <cygwin-talk@cygwin.com>
Subject: Re: FW: question: high virtual memory usage
Date: Tue, 14 Jun 2005 18:36:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.61.0506141158500.4202@slinky.cs.nyu.edu> (raw)
In-Reply-To: <SERRANOXmapMHFVsTUN0000003f@SERRANO.CAM.ARTIMI.COM>
On Tue, 14 Jun 2005, Dave Korn's computer deigned to emit the following stream of bytes:
> ----Original Message----
> >From: Dave Korn
> >Sent: 14 June 2005 10:36
>
> > ----Original Message----
> >> From: Brian Dessent
> >> Sent: 14 June 2005 03:23
> >
> >> Procexp's "virtual size" column seems to be a meaningless number that
> >> procexp somehow arrives at.
> >
> > It's the amount of reserved-but-not-yert-committed memory.
>
> "Yurt-commmitted" memory, of course, is that portion of the process memory
> space reserved for tracking the movements of nomadic mongolian tents;
> apologies for mis-speeling it. D'oh!
And people complain about SETI@home...
OAU
prev parent reply other threads:[~2005-06-14 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 13:42 Dave Korn
2005-06-14 18:36 ` One Angry User [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.61.0506141158500.4202@slinky.cs.nyu.edu \
--to=angry@lusers.org \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).