On Wed, Oct 11, 2006 at 10:15:39AM -0700, Chen, Kenneth W wrote:
> I'm more inclined to define RSS as "how much ram does my application
> cause to be used". To monitor process's working set size, We already
> have /proc/<pid>/smaps. Whether we can use working set size in an
> intelligent way in mm is an interesting question. Though, so far such
> accounting is not utilized at all.
If that is the case, it would make sense to account such things as page
tables and other kernel allocations against the RSS, which would be useful.
That said, it's possible to keep semantics fairly close to those currently
implemented by tracking RSS differently for shared vs private areas --
those vmas which are shared could be placed on a list and then summed when
RSS is read. That said, I'm not sure it is a good idea, as the cost of
obtaining RSS for tools like top is exactly why we have the current
counters maintained to provide O(1) semantics.
All of the old semantics are covered by smaps, though, so I'd agree with
any changes to make RSS reflect allocations incurred by this process.
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <[email protected]>.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
