How come top and /proc/meminfo on 2.4.0 says 0K shared?

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 the
individual procs show the memory they are sharing though.

thanks,
Ian

Here is /proc/meminfo:

total: used: free: shared: buffers: cached:

Mem:  261734400 251297792 10436608        0 12423168 124805120
Swap: 279650304 24297472 255352832
MemTotal:       255600 kB
MemFree:         10192 kB
MemShared:           0 kB
Buffers:         12132 kB
Cached:         121880 kB
Active:          91308 kB
Inact_dirty:     38136 kB
Inact_clean:      4568 kB
Inact_target:     1436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       255600 kB
LowFree:         10192 kB
SwapTotal:      273096 kB
SwapFree:       249368 kB

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

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.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/