From: Rohit Seth <rohitseth@google.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andi Kleen <ak@suse.de>, Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@osdl.org>,
Linux-mm@kvack.org, Linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Adding a counter in vma to indicate the number of physical pages backing it
Date: Tue, 13 Jun 2006 11:09:28 -0700 [thread overview]
Message-ID: <1150222169.17423.21.camel@galaxy.corp.google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606131814110.4501@blonde.wat.veritas.com>
On Tue, 2006-06-13 at 18:28 +0100, Hugh Dickins wrote:
> On Tue, 13 Jun 2006, Rohit Seth wrote:
> > On Tue, 2006-06-13 at 05:51 +0200, Andi Kleen wrote:
> > >
> > > 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).
>
> Then perhaps you want a sys_report_page_activation(pid, start_va, len, ...)
> which would examine and report on the range in question, instead of adding
> your count to so many vmas on which this will never be used.
>
That will reduce the cost of not traversing the whole process address
space. But still for a given length, we will need to traverse the PTs.
On a positive side, this interface can give more specific information to
user in terms of page attributes. I'm fine with this interface if
others are okay. Andi?
> Though your syscall sounds like pid_madvise: perhaps the call name
> should be less specific and left to the flags (come, gentle syscall
> multiplexing flames, and warm me).
>
Agreed.
> Looking through the existing fields of a vma, it seems a vm_area_struct
> would commonly be on clean cachelines: your count making one of them
> now commonly and bouncily dirty.
The additional cost of this counter will be long size of extra memory
per segment, an atomic operation when ptl is used and dirtying an
additional cache line. I overlooked the last two cost factors earlier.
-rohit
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-06-13 18:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 1:33 Rohit Seth
2006-06-10 2:42 ` Andrew Morton
2006-06-12 17:49 ` Rohit Seth
2006-06-10 7:35 ` Nick Piggin
2006-06-11 10:15 ` Jan Engelhardt
2006-06-12 17:36 ` Rohit Seth
2006-06-12 17:58 ` Andi Kleen
2006-06-12 19:42 ` Rohit Seth
2006-06-13 3:51 ` Andi Kleen
2006-06-13 4:27 ` Nick Piggin
2006-06-13 16:59 ` Rohit Seth
2006-06-13 17:28 ` Hugh Dickins
2006-06-13 18:09 ` Rohit Seth [this message]
2006-06-13 17:31 ` Andi Kleen
2006-06-11 16:09 ` Arjan van de Ven
2006-06-12 11:17 ` Andi Kleen
2006-06-12 12:49 ` Jan Engelhardt
2006-06-12 12:54 ` Andi Kleen
2006-06-12 16:43 ` Christoph Lameter
2006-06-13 5:53 [PATCH]: Adding a counter in vma to indicate the number of physical_pages_backing it Albert Cahalan
2006-06-13 5:56 ` Andi Kleen
2006-06-13 17:10 ` Rohit Seth
2006-06-13 17:18 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1150222169.17423.21.camel@galaxy.corp.google.com \
--to=rohitseth@google.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=Linux-mm@kvack.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=nickpiggin@yahoo.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox