From: Rik van Riel <riel@conectiva.com.br>
To: Alexey Zhuravlev <alexey@datafoundation.com>
Cc: linux-mm@kvack.org
Subject: Re: about profiling and stats info for pagecache/buffercache
Date: Sun, 6 May 2001 16:42:04 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0105061636020.582-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <200105061800.OAA20123@datafoundation.com>
On Sun, 6 May 2001, Alexey Zhuravlev wrote:
> As far as I understand, now Linux have no facility to collect stats info
> for pagecache/buffercache. For example, it'd be fine if we can see how
> many requests were submited to pagecache/buffercache and how many of
> these requests was serviced from cache without I/O. Moreover, it'd be fine
> to have some profiling info on requests for pagecache/buffercache...
OK, so you want:
pagecache nr_requests hit mis
buffercache nr_requests hit mis
I'd like to see a few other statistics as well, mainly for the
pageout code...
- nr pages scannned
- nr pages moved to the inactive_clean list
- nr pages "rescued" from the inactive_clean list
- nr pages evicted
- nr pages deactivated by pageout scanning
- nr pages deactivated by drop-behind
Are there any more ideas for statistics people would like to
see?
regards,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/ http://distro.conectiva.com/
Send all your spam to aardvark@nl.linux.org (spam digging piggy)
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-06 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 18:02 Alexey Zhuravlev
2001-05-06 19:42 ` Rik van Riel [this message]
2001-05-07 18:10 ` Stephen C. Tweedie
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=Pine.LNX.4.21.0105061636020.582-100000@imladris.rielhome.conectiva \
--to=riel@conectiva.com.br \
--cc=alexey@datafoundation.com \
--cc=linux-mm@kvack.org \
/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