From: William Lee Irwin III <wli@holomorphy.com>
To: "Roets, Chris (Tru64&Linux support)" <chris.roets@hp.com>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel@vger.kernel.org
Subject: Re: /proc/meminfo
Date: Tue, 3 Jun 2003 23:52:05 -0700 [thread overview]
Message-ID: <20030604065205.GX8978@holomorphy.com> (raw)
In-Reply-To: <224CFA9643B4CE4BA18137CF73DB2F32020E0DC0@broexc01.emea.cpqcorp.net>
At some point in the past, I wrote:
>> (a) boot-time code dropping memory regions on the floor
>> (b) some misunderstanding about reporting in /proc/meminfo
>> This is also different from your other bugreport.
On Wed, Jun 04, 2003 at 06:51:09AM +0200, Roets, Chris wrote:
> [Chris >] 1.4 G is a lot to loose now ?
Your quoting style leaves something to be desired.
What exactly is this chart supposed to say? Are you asking about the
numbers not adding up?
-- wli
next parent reply other threads:[~2003-06-04 6:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <224CFA9643B4CE4BA18137CF73DB2F32020E0DC0@broexc01.emea.cpqcorp.net>
2003-06-04 6:52 ` William Lee Irwin III [this message]
2006-06-06 11:16 /proc/meminfo Abu M. Muttalib
2006-06-06 11:28 ` /proc/meminfo Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 14:36 /proc/meminfo Abu M. Muttalib
2006-06-06 9:37 ` /proc/meminfo Jes Sorensen
2005-05-16 17:25 /proc/meminfo Jared Hulbert
2005-05-16 17:30 ` /proc/meminfo Dave Hansen
2003-11-18 12:11 /proc/meminfo Dan Am
2003-06-03 13:51 /proc/meminfo Roets, Chris (Tru64&Linux support)
2003-06-03 14:05 ` /proc/meminfo William Lee Irwin III
2003-06-02 11:55 /proc/meminfo Roets, Chris (Tru64&Linux support)
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=20030604065205.GX8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=chris.roets@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.