From: "M. Edward Borasky" <znmeb@aracnet.com>
To: "RaúlNúñez de Arenas Coronado" <raul@viadomus.com>,
linux-kernel@vger.kernel.org
Subject: RE: Out of Memory at 20GB of free memory ??
Date: Thu, 27 Dec 2001 07:23:55 -0800 [thread overview]
Message-ID: <HBEHIIBBKKNOBLMPKCBBAEMAEEAA.znmeb@aracnet.com> (raw)
In-Reply-To: <E16JZGx-0000Lc-00@DervishD.viadomus.com>
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of RaúlNúñez de
> Arenas Coronado
> Sent: Thursday, December 27, 2001 4:05 AM
> >/proc/meminfo after the first process kill:
> > total: used: free: shared: buffers: cached:
> >Mem: 33815060480 13490249728 20324810752 0 15745024 13089452032
>
> This leads to a suggestion... How about aligning the top
> indication with the numbers below (or even better, putting them in
> different lines ;)))
>
> Even with more than 99MB of RAM (quite usual these days), the top
> line is misaligned and a little bit confusing.
>
> I can make the necessary patch if anyone is interested.
>
> Raúl
My impression was that the top few lines of /proc/meminfo were being "phased
out" in favor of the one-entry-per-line-in kB numbers below. If that is the
case (and assuming we don't want to change that to KiB or something of that
ilk :) perhaps what needs to change is not /proc/meminfo but "top".
--
M. Edward Borasky
znmeb@borasky-research.net
http://www.borasky-research.net
next prev parent reply other threads:[~2001-12-27 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 12:04 RaúlNúñez de Arenas Coronado
2001-12-27 15:23 ` M. Edward Borasky [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-28 16:26 RaúlNúñez de Arenas Coronado
2001-12-27 11:18 Holzer Harald
2001-12-27 15:23 ` M. Edward Borasky
2001-12-27 16:01 ` M. Edward Borasky
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=HBEHIIBBKKNOBLMPKCBBAEMAEEAA.znmeb@aracnet.com \
--to=znmeb@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raul@viadomus.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
all inboxes | Powered by JetHome®