Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753046AbYKMJFi (ORCPT ); Thu, 13 Nov 2008 04:05:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751497AbYKMJFO (ORCPT ); Thu, 13 Nov 2008 04:05:14 -0500 Received: from fms-01.valinux.co.jp ([210.128.90.1]:58701 "EHLO mail.valinux.co.jp" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751235AbYKMJFM (ORCPT ); Thu, 13 Nov 2008 04:05:12 -0500 Date: Thu, 13 Nov 2008 18:05:58 +0900 (JST) Message-Id: <20081113.180558.519459540419535699.ryov@valinux.co.jp> To: vgoyal@redhat.com Cc: linux-kernel@vger.kernel.org, containers@lists.linux-foundation.org, virtualization@lists.linux-foundation.org, jens.axboe@oracle.com, taka@valinux.co.jp, righi.andrea@gmail.com, s-uchida@ap.jp.nec.com, fernando@oss.ntt.co.jp, balbir@linux.vnet.ibm.com, akpm@linux-foundation.org, menage@google.com, ngupta@google.com, riel@redhat.com, jmoyer@redhat.com, peterz@infradead.org Subject: Re: [patch 0/4] [RFC] Another proportional weight IO controller From: Ryo Tsuruta In-Reply-To: <20081106153022.215696930@redhat.com> References: <20081106153022.215696930@redhat.com> X-Mailer: Mew version 6.1 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2141 Lines: 59 Hi, From: vgoyal@redhat.com Subject: [patch 0/4] [RFC] Another proportional weight IO controller Date: Thu, 06 Nov 2008 10:30:22 -0500 > Hi, > > If you are not already tired of so many io controller implementations, here > is another one. > > This is a very eary very crude implementation to get early feedback to see > if this approach makes any sense or not. > > This controller is a proportional weight IO controller primarily > based on/inspired by dm-ioband. One of the things I personally found little > odd about dm-ioband was need of a dm-ioband device for every device we want > to control. I thought that probably we can make this control per request > queue and get rid of device mapper driver. This should make configuration > aspect easy. > > I have picked up quite some amount of code from dm-ioband especially for > biocgroup implementation. > > I have done very basic testing and that is running 2-3 dd commands in different > cgroups on x86_64. Wanted to throw out the code early to get some feedback. > > More details about the design and how to are in documentation patch. > > Your comments are welcome. Do you have any benchmark results? I'm especially interested in the followings: - Comparison of disk performance with and without the I/O controller patch. - Put uneven I/O loads. Processes, which belong to a cgroup which is given a smaller weight than another cgroup, put heavier I/O load like the following. echo 1024 > /cgroup/bio/test1/bio.shares echo 8192 > /cgroup/bio/test2/bio.shares echo $$ > /cgroup/bio/test1/tasks dd if=/somefile1-1 of=/dev/null & dd if=/somefile1-2 of=/dev/null & ... dd if=/somefile1-100 of=/dev/null echo $$ > /cgroup/bio/test2/tasks dd if=/somefile2-1 of=/dev/null & dd if=/somefile2-2 of=/dev/null & ... dd if=/somefile2-10 of=/dev/null & Thanks, Ryo Tsuruta -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/