>> There is currently /proc/<pid>/smaps that prints the detailed
>> information about the usage of physical pages but that is a very
>> expensive operation as it traverses all the PTs (for some one who is
>> just interested in getting that data for each vma).
>
> Yet more cacheline footprint in the page fault and unmap paths...
>
> What is this used for and why do we want it? Could you do some
> smaps-like interface that can work on ranges of memory, and
> continue to walk pagetables instead?
>
BTW, what is smaps used for (who uses it), anyway?
Jan Engelhardt
--
-
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]