🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: ch.comp.os.linux
Article #12264

memory info falsch?!

#12264
From: Daniel Stirnimann
Date: Sat, 04 Aug 2001 17:21
63 lines
3015 bytes
Hallo Zusammen

Auf meinem Debian 2.2r3 mit Kernel 2.4.5 zeigt 'top' irgendwie einen
unrealistischen Wert f�r den gebrauchten/freien/gesharten Arbeitspeicher
an.

## top ##
6:59pm  up 20 days, 20 min,  0 users,  load average: 0.00, 0.00, 0.00
59 processes: 58 sleeping, 1 running, 0 zombie, 0 stopped
CPU states:  0.7% user, 50.0% system,  0.0% nice, 49.1% idle
Mem:  383848K av, 374104K used,   9744K free,      0K shrd,  16520K buff
Swap: 128516K av,      0K used, 128516K free                249632K cached


## cat /proc/meminfo ##
      total:    used:    free:  shared: buffers:  cached:
Mem:  393060352 382238720 10821632        0 16916480 255623168
Swap: 131600384        0 131600384
MemTotal:       383848 kB
MemFree:         10568 kB
MemShared:           0 kB
Buffers:         16520 kB
Cached:         249632 kB
Active:           9240 kB
Inact_dirty:    256912 kB
Inact_clean:         0 kB
Inact_target:       12 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       383848 kB
LowFree:         10568 kB
SwapTotal:      128516 kB
SwapFree:       128516 kB


Nun, ich habe kurz in google nach einer m�glichen Antwort dazu gesucht.
Das einzige schlau was ich gefunde habe hier:

  From: Andi Kleen (ak@suse.de)
  Subject: Re: How come top and /proc/meminfo on 2.4.0 says 0K shared?
  Newsgroups: mlist.linux.kernel
  View complete thread (2 articles)
  Date: 2001-01-19 10:22:58 PST
  
  On Fri, Jan 19, 2001 at 09:39:13AM -0700, Ian S. Nelson wrote:
  > is this a bug?
  > We have a number of machines running 2.4.0 and /proc/meminfo says 
  > we're sharing no memory.  top says that also, probably because it
  > just reads /proc/meminfo, or at least I assume that's how it works.
  > All theindividual procs show the memory they are sharing though.
  
  It has been removed because the computation involved walking the complete
  memory maps and it caused noticeable scheduling hickups (mouse pointer
  hangs etc.) on big memory machines.

Soll also heissen, dass mir 'top' und '/proc/meminfo' nicht mehr die
aktuellen Werte anzeigen.

Nun meine Frage, wie komme ich an die aktuellen Memory Infos ran?

Merci

Gruss Dani
Technical Details
Message-ID: <20010804.192117.1782436840.16915@sun.stirnimann.home>
Path: arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!news.tele.dk!193.190.198.17!newsfeeds.belnet.be!news.belnet.be!psinet-eu-nl!news.imp.ch!imp.ch!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII
X-Google-Thread: f4b73,e38e7d8ff4e9e71c,start
X-Google-Attributes: gidf4b73,public
X-Google-ArrivalTime: 2001-08-04 10:21:46 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!news.tele.dk!193.190.198.17!newsfeeds.belnet.be!news.belnet.be!psinet-eu-nl!news.imp.ch!imp.ch!not-for-mail
From: "Daniel Stirnimann" <woop@mail.com>
Newsgroups: ch.comp.os.linux
Subject: memory info falsch?!
Date: Sat, 04 Aug 2001 19:21:25 +0200
Organization: ImproWare AG Network Services - Usenet News Service
Lines: 63
Message-ID: <20010804.192117.1782436840.16915@sun.stirnimann.home>
NNTP-Posting-Host: 212.59.154.193
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Pan/0.9.6 (Unix)