Khimenko Victor writes:
> Yeas and no. No, it is NOT normal - shared memory should not be displayed
> as 0. And yes it IS normal since it's well-known problem of VERY low
> priority: it does not trigger bugs in code, it does not crash system and so
> on so we can live with it for 2.4.0. In 2.4.<something-big> it will be fixed,
> I hope.
This has been discussed at long length previously here. You may want
to search the archives. IIRC, it will not be fixed, since the overhead
of calculating it is too great. The only reason the figure remains is
for compatibility with some programs that read /proc/meminfo.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/~rmk/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jul 07 2000 - 21:00:14 EST