From: John Fremlin <vii@users.sourceforge.net>
To: Rik van Riel <riel@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: 25 Jun 2001 22:15:31 +0100 [thread overview]
Message-ID: <m28zigi7m4.fsf@boreas.yi.org.> (raw)
In-Reply-To: <Pine.LNX.4.21.0106251456130.7419-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0106251456130.7419-100000@imladris.rielhome.conectiva> (Rik van Riel's message of "Mon, 25 Jun 2001 14:57:39 -0300 (BRST)")
Rik van Riel <riel@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.
>
> Sounds like a cool idea. One thing you should keep in mind though
> is to gather traces of the WHOLE SYSTEM and not of individual
> applications.
In the current patch all pagefaults are recorded from all sources. I'd
like to be able to catch read(2) and write(2) (buffer cache stuff) as
well but I don't know how . . . .
> There has to be a way to balance the eviction of pages from
> applications against those of other applications.
Of course! It is important not to regard each thread group as an
independent entity IMHO (had a big old argument about this).
[...]
--
http://ape.n3.net
WARNING: multiple messages have this Message-ID (diff)
From: John Fremlin <vii@users.sourceforge.net>
To: Rik van Riel <riel@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: 25 Jun 2001 22:15:31 +0100 [thread overview]
Message-ID: <m28zigi7m4.fsf@boreas.yi.org.> (raw)
In-Reply-To: <Pine.LNX.4.21.0106251456130.7419-100000@imladris.rielhome.conectiva> (Rik van Riel's message of "Mon, 25 Jun 2001 14:57:39 -0300 (BRST)")
Rik van Riel <riel@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.
>
> Sounds like a cool idea. One thing you should keep in mind though
> is to gather traces of the WHOLE SYSTEM and not of individual
> applications.
In the current patch all pagefaults are recorded from all sources. I'd
like to be able to catch read(2) and write(2) (buffer cache stuff) as
well but I don't know how . . . .
> There has to be a way to balance the eviction of pages from
> applications against those of other applications.
Of course! It is important not to regard each thread group as an
independent entity IMHO (had a big old argument about this).
[...]
--
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-25 21:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 15:26 VM tuning through fault trace gathering [with actual code] John Fremlin
2001-06-25 15:26 ` John Fremlin
2001-06-25 17:57 ` Rik van Riel
2001-06-25 17:57 ` Rik van Riel
2001-06-25 21:15 ` John Fremlin [this message]
2001-06-25 21:15 ` John Fremlin
2001-06-25 21:33 ` EXT2 Filesystem permissions (bug)? Shawn Starr
2001-06-25 21:42 ` H. Peter Anvin
2001-06-25 22:20 ` Shawn Starr
2001-06-26 22:23 ` Kenneth Johansson
2001-06-26 22:40 ` Hua Zhong
2001-06-26 23:04 ` Albert D. Cahalan
2001-06-27 0:02 ` Guest section DW
2001-06-27 9:37 ` Luigi Genoni
2001-06-25 21:47 ` Andreas Dilger
2001-06-25 22:10 ` Luigi Genoni
2001-06-26 14:02 ` VM tuning through fault trace gathering [with actual code] Scott F. Kaplan
2001-06-26 19:29 ` John Fremlin
2001-06-26 0:53 ` Marcelo Tosatti
2001-06-26 0:53 ` Marcelo Tosatti
2001-06-26 12:54 ` John Fremlin
2001-06-26 12:54 ` John Fremlin
2001-06-26 13:52 ` Marcelo Tosatti
2001-06-26 13:52 ` Marcelo Tosatti
2001-06-26 15:38 ` John Fremlin
2001-06-26 15:38 ` John Fremlin
2001-06-27 10:09 ` Marcelo Tosatti
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=m28zigi7m4.fsf@boreas.yi.org. \
--to=vii@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.