From: Daniel Phillips <phillips@arcor.de>
To: Mel <mel@csn.ul.ie>, Scott Kaplan <sfkaplan@cs.amherst.edu>
Cc: Bill Huey <billh@gnuppy.monkey.org>,
Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] rmap 14
Date: Mon, 19 Aug 2002 21:50:33 +0200 [thread overview]
Message-ID: <E17gsXp-0000rJ-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44.0208162247590.874-100000@skynet>
On Saturday 17 August 2002 01:02, Mel wrote:
> On Fri, 16 Aug 2002, Scott Kaplan wrote:
> The measure is the time when the script asked the module to read a page.
> The page is read by echoing to a mapanon_read proc entry. It's looking
> like it takes about 350 microseconds to enter the module and perform the
> read. I don't call schedule although it is possible I get scheduled. The only
> way to be sure would be to collect all timing information within the module
> which is perfectly possible. The only trouble is that if the module collects,
> only one test instance can run at a time.
It sounds like you want to try the linux trace toolkit:
http://www.opersys.com/LTT/
--
Daniel
--
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/
next prev parent reply other threads:[~2002-08-19 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 2:07 Rik van Riel
2002-08-16 2:21 ` Bill Huey
2002-08-16 21:02 ` Mel
2002-08-16 21:29 ` Scott Kaplan
2002-08-16 23:02 ` Mel
2002-08-19 19:05 ` Scott Kaplan
2002-08-19 21:04 ` Mel
2002-08-20 18:41 ` Stephen C. Tweedie
2002-08-21 18:03 ` Mel
2002-08-21 15:05 ` Scott Kaplan
2002-08-21 16:28 ` Mel
2002-08-21 18:39 ` Scott Kaplan
2002-08-19 19:50 ` Daniel Phillips [this message]
2002-08-19 21:19 ` Mel
2002-08-19 21:38 ` Daniel Phillips
2002-08-19 18:04 ` Daniel Phillips
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=E17gsXp-0000rJ-00@starship \
--to=phillips@arcor.de \
--cc=billh@gnuppy.monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=riel@conectiva.com.br \
--cc=sfkaplan@cs.amherst.edu \
/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