> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Muli Ben-Yehuda > Sent: Wednesday, January 12, 2005 11:57 AM > To: Tzahi Fadida > Cc: linux-il@cs.huji.ac.il > Subject: Re: Getting io statistics on processes. > > > On Wed, Jan 12, 2005 at 02:39:03AM +0200, Tzahi Fadida wrote: > .. > > also, by my understanding the dirtied buffer > > relate to memory and swap file? and not directly to files? > > Which kernel version are you looking at? > A dirtied buffer will have to be flushed to disk at some > point, that's why it's interesting.
Well, I have kernel 2.4.27 at home but the target computer have 2.6.3-7mdk mandrake kernel. Lets see if I understand, a dirtied buffer is not a regular file read/write related but only a buffer I allocated in a process using malloc, etc... that was changed and needed to be returned to the vm swap file. The question is, how do I know its my process dirtied buffer being written. for example, how do I find out that kupdated: READ block 475474/2 on 03:05 or kupdated: WRITE block 180266/2 on 03:05 was caused by my program memory manipulations. p.s: the 475474 is bh->b_rsector in the code which probably literaly means the sector on a disc. > > Cheers, > Muli > -- > Muli Ben-Yehuda > http://www.mulix.org | http://mulix.livejournal.com/ > > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
