mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dong-Jae Kang" <baramsori72@gmail.com>
To: "Ryo Tsuruta" <ryov@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
	containers@lists.linux-foundation.org,
	virtualization@lists.linux-foundation.org,
	xen-devel@lists.xensource.com, agk@sourceware.org,
	fernando@oss.ntt.co.jp, xemul@openvz.org,
	balbir@linux.vnet.ibm.com
Subject: Re: [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.7.0: Introduction
Date: Wed, 8 Oct 2008 17:29:34 +0900	[thread overview]
Message-ID: <2891419e0810080129sb6b35y11362f4bef71c174@mail.gmail.com> (raw)
In-Reply-To: <20081003.143749.193701570.ryov@valinux.co.jp>

[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]

Hi, Ryo Tsuruta

I tested dm-ioband( the latest release, ver 1.7.0 ) IO controller, but
I had a strange result from it.
I have something wrong in test process?
The test process and results are in attached file.
Can you check my testing result and give me a helpful advices and comments?

As you can show in attached file, I tested 4 cases in dm-ioband with
tiobench() IO testing tool like as below
-	1) 3 cgroups with different weight in same ioband device(ioband1) :
Buffered IO
-	2) 3 cgroups with different weight in same ioband device(ioband1) : Direct IO
-	3) 3 cgroups with different weight in each ioband divice(ioband1, 2,
3) : Buffered IO
-	4) 3 cgroups with different weight in each ioband divice(ioband1, 2,
3) : Direct IO
But, IO bandwidth was not nearly controlled by dm-ioband

You can refer the testing tool, tiobench, in
http://sourceforge.net/projects/tiobench/
Originally, tiobench don't support the direct IO mode testing, so I
added the O_DIRECT option to tiobench source code and recompile it to
test the Direct IO cases

Thanks,
Dong-Jae, Kang

---------------------------------------------------------------------
2008/10/3 Ryo Tsuruta <ryov@valinux.co.jp>:
> Hi everyone,
>
> This is the dm-ioband version 1.7.0 release.
>
> Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
> driver, which gives specified bandwidth to each job running on the same
> physical device.
>
> - Can be applied to the kernel 2.6.27-rc5-mm1.
> - Changes from 1.6.0 (posted on Sep 24, 2008):
>  - Fix a problem that processes issuing I/Os are permanently blocked
>    when I/O requests to reclaim pages are consecutively issued.
>
> You can apply the latest bio-cgroup patch to this dm-ioband version.
> The bio-cgroup provides a BIO tracking mechanism with dm-ioband.
> Please see the following site for more information:
>  Block I/O tracking
>  http://people.valinux.co.jp/~ryov/bio-cgroup/
>
> Thanks,
> Ryo Tsuruta
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
>

[-- Attachment #2: dm-ioband_test_result.pdf --]
[-- Type: application/pdf, Size: 69828 bytes --]

  parent reply	other threads:[~2008-10-08  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03  5:37 Ryo Tsuruta
2008-10-03  5:38 ` [PATCH 1/2] dm-ioband: I/O bandwidth controller v1.7.0: Source code and patch Ryo Tsuruta
2008-10-03  5:39   ` [PATCH 2/2] dm-ioband: I/O bandwidth controller v1.7.0: Document Ryo Tsuruta
2008-10-08  8:29 ` Dong-Jae Kang [this message]
2008-10-08 10:40   ` [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.7.0: Introduction Ryo Tsuruta
2008-10-09  6:15     ` Dong-Jae Kang
2008-10-09 12:14       ` Ryo Tsuruta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2891419e0810080129sb6b35y11362f4bef71c174@mail.gmail.com \
    --to=baramsori72@gmail.com \
    --cc=agk@sourceware.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryov@valinux.co.jp \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xemul@openvz.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®