From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32372 invoked by alias); 25 Apr 2008 11:31:46 -0000 Received: (qmail 32214 invoked by uid 48); 25 Apr 2008 11:31:04 -0000 Date: Fri, 25 Apr 2008 11:31:00 -0000 From: "mark at klomp dot org" To: frysk-bugzilla@sourceware.org Message-ID: <20080425113103.6457.mark@klomp.org> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/6457] New: Provide I/O traces for iogrind X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00112.txt.bz2 List-Id: iogrind is a prototype I/O profiling tool. http://live.gnome.org/iogrind It aims to give a fairly accurate picture of all the I/O your application would perform on a cold start. It has three parts: 1. tracing the application using valgrind 2. snapshotting the filesystem 3. simulating the trace, against a snapshot to visualise. It would be nice to provide the first part as a systemtap script. It would basically need to provide a trace of all file accesses (open, stat, chmod, unlink, ...) + all 1st time memory page touches. -- Summary: Provide I/O traces for iogrind Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: mark at klomp dot org http://sourceware.org/bugzilla/show_bug.cgi?id=6457 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.