[lkml]   [2010]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/4] io-controller: Add new interfaces to trace backlogged group status
On Mon, May 24, 2010 at 09:12:05AM +0800, Gui Jianfeng wrote:
> Vivek Goyal wrote:
> > On Fri, May 21, 2010 at 04:40:50PM +0800, Gui Jianfeng wrote:
> >> Hi,
> >>
> >> This series implements three new interfaces to keep track of tranferred bytes,
> >> elapsing time and io rate since group getting backlogged. If the group dequeues
> >> from service tree, these three interfaces will reset and shows zero.
> >
> > Hi Gui,
> >
> > Can you give some details regarding how this functionality is useful? Why
> > would somebody be interested in only in stats of till group was
> > backlogged and not in total stats?
> >
> > Groups can come and go so fast and these stats will reset so many times
> > that I am not able to visualize how these stats will be useful.
> Hi Vivek,
> Currently, we assign weight to a group, but user still doesn't know how fast the
> group runs. With io rate interface, users can check the rate of a group at any
> moment, or to determine whether the weight assigned to a group is enough.
> bytes and time interface is just for debug purpose.


I still don't understand that why blkio.sectors or blkio.io_service_bytes
or blkio.io_serviced interfaces are not good enough to determine at what
rate a group is doing IO.

I think we can very well write something in userspace like "iostat" to
display the per group rate. Utility can read the any of the above files
say at the interfval of 1s, calculate the diff between the values and
display that as group effective rate.


 \ /
  Last update: 2010-05-24 23:25    [W:0.045 / U:23.120 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site