From: John Fremlin <vii@users.sourceforge.net>
To: Scott F <Kaplan@boreas.yi.org.>
Cc: linux-mm@kvack.org
Subject: Re: VM tuning through fault trace gathering [with actual code]
Date: 26 Jun 2001 20:29:16 +0100 [thread overview]
Message-ID: <m21yo7hwfn.fsf@boreas.yi.org.> (raw)
In-Reply-To: <01062610022607.01124@spigot> (Scott F. Kaplan's message of "Tue, 26 Jun 2001 10:02:26 -0400")
Hi people!
I just sent an updated version of the patch to Scott, which faults on
almost every mem access. Unfortunately that slows the system to a
crawl (doh), in fact so much of a crawl that nothing much
happens. Anybody have a turbofast P4/Athlon they want to lend or send
me ;-)
Scott F. Kaplan <sfkaplan@cs.amherst.edu> writes:
[...]
> Not to look a gift horse in the mouth, but the ability to trace
> selectively either the whole system OR an individual application
> would be useful. Certainly whole system traces would be new, as
> individual process traces can be gathered with other tools (although
> I don't know of one available on Linux -- I'm stuck using ATOM under
> Alpha/Tru64.)
That looks like a very cool package (AFAICS it instruments the binary
to call a subroutine before every memory access).
The pagetrace patch has a slightly different goal however. The alpha
people seemed to want to tune their cache behaviour whereas I want to
tune the VM behaviour.
> > 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 . . . .
>
> Also a great idea. Someone who works on the filesystem end of the
> kernel should be able to add support for this kind of thing without
> much trouble, don't you think?
I'd really like a clue or too in this direction certainly because its
difficult to simulate the VM if you don't know how big e.g. the
directory dcache is.
> > Of course! It is important not to regard each thread group as an
> > independent entity IMHO (had a big old argument about this).
>
> Yes, I was the other side of that argument! :-) I'll still contend that,
Hehe. Let's not go into that right now ;-)
[...]
--
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 19:29 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
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 [this message]
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=m21yo7hwfn.fsf@boreas.yi.org. \
--to=vii@users.sourceforge.net \
--cc=Kaplan@boreas.yi.org. \
--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 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.