OpenVZ Forum


Home » Mailing lists » Devel » Re: [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview
Re: [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview [message #26423] Wed, 23 January 2008 14:32 Go to next message
Peter Zijlstra is currently offline  Peter Zijlstra
Messages: 61
Registered: September 2006
Member
On Wed, 2008-01-23 at 21:53 +0900, Ryo Tsuruta wrote:
> Hi everyone,
> 
> I'm happy to announce that I've implemented a Block I/O bandwidth controller.
> The controller is designed to be of use in a cgroup or virtual machine
> environment. The current approach is that the controller is implemented as
> a device-mapper driver.

What definition of bandwidth does it use? Does it for example account
for seek latency?


_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
Re: [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview [message #26444 is a reply to message #26423] Wed, 23 January 2008 17:25 Go to previous message
Ryo Tsuruta is currently offline  Ryo Tsuruta
Messages: 35
Registered: January 2008
Member
Hi Peter,

> What definition of bandwidth does it use? Does it for example account
> for seek latency?

The bandwidth in dm-band is determined by the proportion of the
processing time of each device's tokens(I/Os) to the processing time
of all device's tokens(I/Os).
The processing time of one token(I/O) is determined by one I/O cycle 
include seek latency, interrupt latency, etc...

Thanks,
Ryo Tsuruta <ryov@valinux.co.jp>
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
Previous Topic: [PATCH 0/12 net-2.6.25] [NETNS]: Routing namespacing on IP output path.
Next Topic: Re: LTP result output for container-init
Goto Forum:
  


Current Time: Sat Jul 13 15:13:53 GMT 2024

Total time taken to generate the page: 0.02247 seconds