Re: Inconsistancies in /proc (status vs statm) leading to wrong documentation(proc.txt)

[Eric Valette]

Albert Cahalan wrote:

> The documentation is incorrect. It was written to match a buggy
> implementation in early 2.6.x kernels.

Well the Documentation is said to matches 2.6.8-rc3 and is only 5 weeks 
old according to bitkeeper changesets... So at least the doc should be 
fixed.

> VmSize is the address space occupied, excluding memory-mapped IO.
> The statm value is the address space occupied.

Why removing memory-mapped IO in one case (status) and not the other 
(statm)? Memory mapped IO, may of course reserve some physical memory 
pages for establishing the mmu->phys adress translation table (if any) 
but not really the amount of space mapped.

> > May I suggest :
> > - To use consistent memory size units between status and statm,

> No way. This would instantly break the "top" program.

OK. Too bad because statm is hardly readable but I guess it is not for 
human then...

Thanks for responding,

-- eric

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/