On Tue, 2006-06-13 at 05:51 +0200, Andi Kleen wrote:
> On Monday 12 June 2006 21:42, Rohit Seth wrote:
>
> > I think having this information in each vma keeps the impact (of adding new counter) to very
> > low.
> >
> > Second question is to advertize this value to user space. Please let me
> > know what suites the most among /proc, /sys or system call (or if there
> > is any other mechanism then let me know) for a per process per segment
> > related information.
>
> I think we first need to identify the basic need.
> Don't see why we even need per VMA information so far.
This information is for user land applications to have the knowledge of
which virtual ranges are getting actively used and which are not.
This information then can be fed into a new system call
sys_change_page_activation(pid, start_va, len, flag). The purpose of
this system call would be to give hints to kernel that certain physical
pages are okay to be inactivated (or vice versa).
-rohit
-
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]
