On Thu, May 03 2001, Shaun wrote:
> Again, this isn't the case in the 2.2.16 kernel I'm working with. Each
> call to make_request() causes pgin/pgout to be incremented, since these
> requests can be of different sizes (even for the same disk) I can't see
> how a kb value can be deduced.
Check if
> > In regards to diskr/wblk, drive_stat_acct() increments the number of
> > sectors/blocks read based n the values in the request being processed by
> > add_request(). But add_request() is only called for requests that can't be
> > merged with requests currently on the queue. Thus the counters c
On Wed, May 02 2001, Shaun wrote:
> In regards to diskr/wblk, drive_stat_acct() increments the number of
> sectors/blocks read based n the values in the request being processed by
> add_request(). But add_request() is only called for requests that can't be
> merged with requests currently on the q
Hi All,
I've now been battling for several days with the kernel performance stats
for disks and have come to the conclusion I need some assistance from
someone with a little more understanding of the block device support in
the kernel (and the kernel in general).
Initially I've been looking at
4 matches
Mail list logo
