From: John Fremlin <vii@users.sourceforge.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: VM tuning through fault trace gathering [with actual code]
Date: 26 Jun 2001 13:54:30 +0100 [thread overview]
Message-ID: <m2n16vcsft.fsf@boreas.yi.org.> (raw)
In-Reply-To: <Pine.LNX.4.21.0106252152580.941-100000@freak.distro.conectiva> (Marcelo Tosatti's message of "Mon, 25 Jun 2001 21:53:33 -0300 (BRT)")
Marcelo Tosatti <marcelo@conectiva.com.br> writes:
> On 25 Jun 2001, John Fremlin wrote:
>
> >
> > Last year I had the idea of tracing the memory accesses of the system
> > to improve the VM - the traces could be used to test algorithms in
> > userspace. The difficulty is of course making all memory accesses
> > fault without destroying system performance.
[...]
> Linux Trace Toolkit (http://www.opersys.com/LTT) does that.
I dld the ltt-usenix paper and skim read it. It didn't seem to talk
about page faults much. Where should I look?
--
http://ape.n3.net
--
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:[~2001-06-26 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 15:26 John Fremlin
2001-06-25 17:57 ` Rik van Riel
2001-06-25 21:15 ` John Fremlin
2001-06-26 14:02 ` Scott F. Kaplan
2001-06-26 19:29 ` John Fremlin
2001-06-26 0:53 ` Marcelo Tosatti
2001-06-26 12:54 ` John Fremlin [this message]
2001-06-26 13:52 ` Marcelo Tosatti
2001-06-26 15:38 ` John Fremlin
2001-06-27 10:09 ` Marcelo Tosatti
2001-06-27 12:47 ` Scott F. Kaplan
2001-06-27 13:51 ` Marcelo Tosatti
2001-06-27 16:05 ` John Fremlin
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=m2n16vcsft.fsf@boreas.yi.org. \
--to=vii@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
/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