MantisBT - VTK
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001119VTK(No Category)public2004-08-29 19:372016-08-12 09:54
ReporterFrançois Bertel 
Assigned ToJulien Jomier 
PrioritylowSeverityfeatureReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Project
Type
Summary0001119: vtkKWProcessStatistics TestMemory
DescriptionSince kernel 2.6, the format of /proc/meminfo changed.
Ref: http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt [^]
or
http://www.kerneltraffic.org/kernel-traffic/kt20030730_224.html [^]

"
procps.
~~~~~~~
- The 2.6 /proc filesystems changed some statistics, which confuse older
  versions of procps. Rik van Riel and Robert Love have been maintaining a
  version of procps during the development of 2.6 which tracks changes to
  /proc which you can find at http://tech9.net/rml/procps/ [^]
- Alternatively, the procps by Albert Cahalan now supports the altered formats
  since v3.0.5 -- http://procps.sf.net/ [^]
- The /proc/meminfo format changed slightly which also broke gtop in strange
  ways. Likely this also broke some of the KDE/GNOME panel applets.
"

For instance, on my laptop with a Mandrake Linux 10.0, kernel 2.6.3, the contents is:
MemTotal: 1034284 kB
MemFree: 9444 kB
Buffers: 58280 kB
Cached: 681176 kB
SwapCached: 19576 kB
Active: 834108 kB
Inactive: 81968 kB
HighTotal: 130744 kB
HighFree: 252 kB
LowTotal: 903540 kB
LowFree: 9192 kB
SwapTotal: 1028120 kB
SwapFree: 960084 kB
Dirty: 140 kB
Writeback: 0 kB
Mapped: 236452 kB
Slab: 83344 kB
Committed_AS: 535552 kB
PageTables: 2428 kB
VmallocTotal: 114680 kB
VmallocUsed: 43552 kB
VmallocChunk: 66740 kB

The format on previous kernel was:

root: total: used: free: shared: buffers: cached:
Mem: 1055760384 1041887232 13873152 0 100417536 711233536
Swap: 1077501952 8540160 1068961792
    
On the RedHat web site, the result of
cat /proc/meminfo gives both format.
http://www.redhat.com/advice/tips/meminfo.html [^]

Hence, I don't know if the format I have is
Mandrake specific or Linux kernel 2.6 specific.

If I run paraview-build/bin/TestMemory
With Mandrake Linux 10, the result is:

Total physical: 0
     Available: 0
 Total virtual: 0
     Available: 0

In fact, in Common/KWCommon/vtkKWProcessStatistics.cxx
in QueryMemory(), the Linux implementation
rely on the old format of /proc/meminfo.


We need to know first the result of TestMemory under other kernels 2.6 on other distributions and also the
result of cat /proc/meminfo for those kernels

If we have to deals with different versions of
Linux, it has to be done at run-time, not at
compile time.

hence, we need first a call to uname (man 2 uname, #include <sys/utsname.h>)
to know what to scan in /proc/meminfo.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2007-08-08 14:57Luis IbanezNote Edited: 0008252
2007-08-08 14:58Luis IbanezSummaryGoodsite => vtkKWProcessStatistics TestMemory
2007-08-08 14:59Luis IbanezProject@6@ => VTK
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2016-08-12 09:54Kitware RobotNote Added: 0036747
2016-08-12 09:54Kitware RobotStatusexpired => closed
2016-08-12 09:54Kitware RobotResolutionfixed => moved

Notes
(0008252)
   
2007-07-28 09:45   
(edited on: 2007-08-08 14:57)
removing spam message from this note.
(0036747)
Kitware Robot   
2016-08-12 09:54   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page.