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

[Andi Kleen]

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 the
> individual 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.

-Andi