Re: Better pagecache statistics ?

Badari Pulavarty
2005-12-02T23:46:35Z

[-- Attachment #1: Type: text/plain, Size: 2481 bytes --]

On Fri, 2005-12-02 at 17:46 -0500, Frank Ch. Eigler wrote:
> Hi -
>
> On Fri, Dec 02, 2005 at 02:31:56PM -0800, Badari Pulavarty wrote:
> > On Fri, 2005-12-02 at 17:15 -0500, Frank Ch. Eigler wrote:
> > [...]
> > > #! stap
> > > probe kernel.function("add_to_page_cache") {
> > > printf("pid %d added pages (%d)\n", pid(), $mapping->nrpages)
> > > }
> > > probe kernel.function("__remove_from_page_cache") {
> > > printf("pid %d removed pages (%d)\n", pid(), $page->mapping->nrpages)
> > > }
> >
> > [...] Having by "pid" basis is not good enough. I need per
> > file/mapping basis collected and sent to user-space on-demand.
>
> If you can characterize all your data needs in terms of points to
> insert hooks (breakpoint addresses) and expressions to sample there,
> systemtap scripts can probably track the relationships. (We have
> associative arrays, looping, etc.)
>
> > Is systemtap hooked to relayfs to send data across to user-land ?
> > printf() is not an option.
>
> systemtap can optionally use relayfs. The printf you see here does
> not relate to/invoke the kernel printk, if that's what you're worried
> about.

Hmm. You are right.

Is there a way another user-level program/utility access some of the
data maintained in those arrays ?

>
> > And also, I need to have this probe, installed from the boot time
> > and collecting all the information - so I can access it when I need
> > it
>
> We haven't done much work yet to address on-demand kind of interaction
> with a systemtap probe session. However, one could fake it by
> associating data-printing operations with events that are triggered
> purposely from userspace, like running a particular system call from a
> particularly named process.
>
> > which means this bloats kernel memory. [...]
>
> The degree of bloat is under the operator's control: systemtap only
> uses initialization-time memory allocation, so its arrays can fill up.

Does this mean that I can do something like

page_cache[0xffff8100c4c6b298] = $mapping->nrpages ?

And this won't generate bloated arrays ?

Here is what I wrote earlier to capture some of the pagecache data.
Unfortunately, I can't capture whatever happend before inserting the
problem. So it won't give me information about all whats there in the
pagecache.

BTW, if you prefer - we can move the discussion to systemtap.
(I have few questions/issues on ret probes & accessability of
arguments - since I want to do this on return).

Thanks,
Badari

[-- Attachment #2: pagecache.stp --]
[-- Type: text/plain, Size: 502 bytes --]

#! stap

global page_cache_pages

function _(n) { return string(n) }

probe kernel.function("add_to_page_cache") {
page_cache_pages[$mapping] = $mapping->nrpages
}

probe kernel.function("__remove_from_page_cache") {
page_cache_pages[$page->mapping] = $page->mapping->nrpages
}

function report () {
foreach (mapping in page_cache_pages) {
print("mapping = " . hexstring(mapping) .
" nrpages = " . _(page_cache_pages[mapping]) . "\n")
}
delete page_cache_pages
}

probe end {
report()
}