From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16860 invoked by alias); 1 Jun 2006 05:57:00 -0000 Received: (qmail 16812 invoked by uid 22791); 1 Jun 2006 05:57:00 -0000 X-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_40 X-Spam-Check-By: sourceware.org Received: from mga02.intel.com (HELO orsmga101-1.jf.intel.com) (134.134.136.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 01 Jun 2006 05:56:57 +0000 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101-1.jf.intel.com with ESMTP; 31 May 2006 22:56:56 -0700 Received: from scsmsx331.sc.intel.com (HELO scsmsx331.amr.corp.intel.com) ([10.3.90.4]) by orsmga001.jf.intel.com with ESMTP; 31 May 2006 22:56:54 -0700 X-IronPort-AV: i="4.05,195,1146466800"; d="scan'208"; a="44176806:sNHT85992704" Received: from scsmsx404.amr.corp.intel.com ([10.3.90.20]) by scsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 31 May 2006 22:56:53 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Fwd: Systemtap support for disk i/o per pid Date: Thu, 01 Jun 2006 05:57:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Fwd: Systemtap support for disk i/o per pid Thread-Index: AcaC6psH3IfTuISWQMi6gi//E4CTDwCSf1Cw From: "Nguyen, Thang P" To: "Li Guanglei" , "James Dickens" Cc: X-OriginalArrivalTime: 01 Jun 2006 05:56:53.0697 (UTC) FILETIME=[2ED85B10:01C68540] X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q2/txt/msg00522.txt.bz2 As for disk I/O, currently I am also adding more hooks into ioscheduler tapset to track disk activities such as block I/O location and estimate disk seek time. Li, I can send you what I have, and see where to fit (or perhaps consolidate) them if necessary. Thang -----Original Message----- From: systemtap-owner@sourceware.org [mailto:systemtap-owner@sourceware.org] On Behalf Of Li Guanglei Sent: Sunday, May 28, 2006 11:39 PM To: James Dickens Cc: systemtap@sourceware.org Subject: Re: Fwd: Systemtap support for disk i/o per pid James Dickens ??: > resending due to improper mime type on the original >=20 > it would be simpler in most cases to probe syscalls that are easily > trackable to pid's though this won't give a totally accurate of IO > because of caching, but it is the easiest, and safest. When you go to > lower level kernel interfaces it becomes difficult to attiribute > actions with the pid that caused them. >=20 > James Dickens > uadmin.blogspot.com Currently Systemtap could make you able to trace all syscalls by pid, e.g: stap -e "probe addevent.syscall {} " -x pid to trace both entry & return of all syscalls or: stap -e "probe addevent.syscall {}" -c command I am getting started with Jose to implement new hooks about IO system=20 calls which could give more details other than the syscall name. And=20 we are also trying to map systemcall to the io scheduler and scsi hooks. - Li Guanglei