On 26 Jun 2001, John Fremlin wrote:
> 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?
Grab the source and try it out?
Example page fault trace:
####################################################################
Event Time PID Length Description
####################################################################
Trap entry 991,299,585,597,016 678 12 TRAP: page fault; EIP : 0x40067785
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 30 2001 - 21:00:14 EST