From: Vivek Goyal <vgoyal@redhat.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org, agk@redhat.com
Subject: Re: dm-ioband: Test results.
Date: Mon, 13 Apr 2009 22:49:43 -0400 [thread overview]
Message-ID: <20090414024943.GA976@redhat.com> (raw)
In-Reply-To: <20090413144626.GF18007@redhat.com>
On Mon, Apr 13, 2009 at 10:46:26AM -0400, Vivek Goyal wrote:
> On Mon, Apr 13, 2009 at 01:05:52PM +0900, Ryo Tsuruta wrote:
> > Hi Alasdair and all,
> >
> > I did more tests on dm-ioband and I've posted the test items and
> > results on my website. The results are very good.
> > http://people.valinux.co.jp/~ryov/dm-ioband/test/test-items.xls
> >
>
> Hi Ryo,
>
> I quickly looked at the xls sheet. Most of the test cases seem to be
> direct IO. Have you done testing with buffered writes/async writes and
> been able to provide service differentiation between cgroups?
>
> For example, two "dd" threads running in two cgroups doing writes.
>
Just realized that last time I replied to wrong mail id. Ryo, this time
you should get the mail. This is reply to my original reply.
Also I wanted to test run your patches. How do I do that? I see that your
patches are based on dm quilt tree. I downloaded the dm-patches and tried
to apply on top of 2.6.30-rc1 but it failed. So can't apply your patches
now.
So what's the simplest way of testing your changes on latest kernels?
Thanks
Vivek
Applying patch dm-add-request-based-facility.patch
patching file drivers/md/dm-table.c
Hunk #1 succeeded at 1021 (offset 29 lines).
patching file drivers/md/dm.c
Hunk #1 succeeded at 90 (offset 6 lines).
Hunk #2 succeeded at 175 (offset -1 lines).
Hunk #3 succeeded at 427 (offset 6 lines).
Hunk #4 succeeded at 648 (offset 10 lines).
Hunk #5 succeeded at 1246 with fuzz 2 (offset 20 lines).
Hunk #6 succeeded at 1273 (offset 3 lines).
Hunk #7 succeeded at 1615 with fuzz 1 (offset 20 lines).
Hunk #8 succeeded at 2016 with fuzz 1 (offset 14 lines).
Hunk #9 succeeded at 2141 (offset 33 lines).
Hunk #10 FAILED at 2321.
Hunk #11 FAILED at 2336.
Hunk #12 succeeded at 2388 with fuzz 2 (offset 29 lines).
2 out of 12 hunks FAILED -- rejects in file drivers/md/dm.c
patching file drivers/md/dm.h
patching file include/linux/device-mapper.h
Hunk #1 succeeded at 230 (offset -1 lines).
Patch dm-add-request-based-facility.patch does not apply (enforce with -f)
> Thanks
> Vivek
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: agk@redhat.com, dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: dm-ioband: Test results.
Date: Mon, 13 Apr 2009 22:49:43 -0400 [thread overview]
Message-ID: <20090414024943.GA976@redhat.com> (raw)
In-Reply-To: <20090413144626.GF18007@redhat.com>
On Mon, Apr 13, 2009 at 10:46:26AM -0400, Vivek Goyal wrote:
> On Mon, Apr 13, 2009 at 01:05:52PM +0900, Ryo Tsuruta wrote:
> > Hi Alasdair and all,
> >
> > I did more tests on dm-ioband and I've posted the test items and
> > results on my website. The results are very good.
> > http://people.valinux.co.jp/~ryov/dm-ioband/test/test-items.xls
> >
>
> Hi Ryo,
>
> I quickly looked at the xls sheet. Most of the test cases seem to be
> direct IO. Have you done testing with buffered writes/async writes and
> been able to provide service differentiation between cgroups?
>
> For example, two "dd" threads running in two cgroups doing writes.
>
Just realized that last time I replied to wrong mail id. Ryo, this time
you should get the mail. This is reply to my original reply.
Also I wanted to test run your patches. How do I do that? I see that your
patches are based on dm quilt tree. I downloaded the dm-patches and tried
to apply on top of 2.6.30-rc1 but it failed. So can't apply your patches
now.
So what's the simplest way of testing your changes on latest kernels?
Thanks
Vivek
Applying patch dm-add-request-based-facility.patch
patching file drivers/md/dm-table.c
Hunk #1 succeeded at 1021 (offset 29 lines).
patching file drivers/md/dm.c
Hunk #1 succeeded at 90 (offset 6 lines).
Hunk #2 succeeded at 175 (offset -1 lines).
Hunk #3 succeeded at 427 (offset 6 lines).
Hunk #4 succeeded at 648 (offset 10 lines).
Hunk #5 succeeded at 1246 with fuzz 2 (offset 20 lines).
Hunk #6 succeeded at 1273 (offset 3 lines).
Hunk #7 succeeded at 1615 with fuzz 1 (offset 20 lines).
Hunk #8 succeeded at 2016 with fuzz 1 (offset 14 lines).
Hunk #9 succeeded at 2141 (offset 33 lines).
Hunk #10 FAILED at 2321.
Hunk #11 FAILED at 2336.
Hunk #12 succeeded at 2388 with fuzz 2 (offset 29 lines).
2 out of 12 hunks FAILED -- rejects in file drivers/md/dm.c
patching file drivers/md/dm.h
patching file include/linux/device-mapper.h
Hunk #1 succeeded at 230 (offset -1 lines).
Patch dm-add-request-based-facility.patch does not apply (enforce with -f)
> Thanks
> Vivek
next prev parent reply other threads:[~2009-04-14 2:49 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 4:05 dm-ioband: Test results Ryo Tsuruta
2009-04-13 14:46 ` Vivek Goyal
2009-04-13 14:46 ` Vivek Goyal
2009-04-14 2:49 ` Vivek Goyal [this message]
2009-04-14 2:49 ` Vivek Goyal
2009-04-14 5:27 ` Ryo Tsuruta
2009-04-14 9:30 ` Ryo Tsuruta
2009-04-14 9:30 ` [dm-devel] " Ryo Tsuruta
2009-04-15 17:04 ` Vivek Goyal
2009-04-15 17:04 ` [dm-devel] " Vivek Goyal
2009-04-16 12:56 ` Ryo Tsuruta
2009-04-16 12:56 ` Ryo Tsuruta
2009-04-16 13:32 ` Vivek Goyal
2009-04-16 13:32 ` [dm-devel] " Vivek Goyal
2009-04-15 4:37 ` Vivek Goyal
2009-04-15 4:37 ` Vivek Goyal
2009-04-15 13:38 ` Ryo Tsuruta
2009-04-15 14:10 ` Vivek Goyal
2009-04-15 14:10 ` Vivek Goyal
2009-04-15 16:17 ` Vivek Goyal
2009-04-15 16:17 ` Vivek Goyal
2009-04-16 2:47 ` [dm-devel] " Ryo Tsuruta
2009-04-16 14:11 ` Vivek Goyal
2009-04-16 14:11 ` [dm-devel] " Vivek Goyal
2009-04-16 20:24 ` Nauman Rafique
2009-04-20 8:29 ` Ryo Tsuruta
2009-04-20 8:29 ` [dm-devel] " Ryo Tsuruta
2009-04-20 9:07 ` Nauman Rafique
2009-04-21 12:06 ` Ryo Tsuruta
2009-04-21 12:10 ` Ryo Tsuruta
2009-04-21 12:10 ` [dm-devel] " Ryo Tsuruta
2009-04-21 13:57 ` Mike Snitzer
2009-04-21 13:57 ` Mike Snitzer
2009-04-21 14:16 ` Vivek Goyal
2009-04-21 14:16 ` Vivek Goyal
2009-04-22 0:50 ` Li Zefan
2009-04-22 3:14 ` Ryo Tsuruta
2009-04-22 3:14 ` [dm-devel] " Ryo Tsuruta
2009-04-22 15:18 ` Mike Snitzer
2009-04-22 15:18 ` Mike Snitzer
2009-04-27 10:30 ` Ryo Tsuruta
2009-04-27 10:30 ` Ryo Tsuruta
2009-04-27 12:44 ` Ryo Tsuruta
2009-04-27 12:44 ` Ryo Tsuruta
2009-04-27 13:03 ` Mike Snitzer
2009-04-27 13:03 ` Mike Snitzer
2009-04-20 21:37 ` Vivek Goyal
2009-04-20 21:37 ` [dm-devel] " Vivek Goyal
2009-04-21 12:18 ` Ryo Tsuruta
2009-04-16 20:57 ` Vivek Goyal
2009-04-16 20:57 ` Vivek Goyal
2009-04-17 2:11 ` Vivek Goyal
2009-04-17 2:11 ` Vivek Goyal
2009-04-17 2:28 ` Vivek Goyal
2009-04-17 2:28 ` Vivek Goyal
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=20090414024943.GA976@redhat.com \
--to=vgoyal@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryov@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.