From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: linux-kernel@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: [RFC] Block IO Controller V2 - some results
Date: Mon, 16 Nov 2009 16:32:15 -0500 [thread overview]
Message-ID: <1258407135.3533.152.camel@cail> (raw)
In-Reply-To: <20091116211412.GJ13235@redhat.com>
On Mon, 2009-11-16 at 16:14 -0500, Vivek Goyal wrote:
> On Mon, Nov 16, 2009 at 03:51:00PM -0500, Alan D. Brunelle wrote:
> > Hi Vivek:
> >
> > I'm finding some things that don't quite seem right - executive
> > summary:
>
> Hi Alan,
>
> Thanks a lot for such an extensive testing and test results. I am still
> digesting the results but I thought I will make a quick note about writes.
> This patchset works only for sync IO. If you are performing buffered
> writes then you will not see any service differentiation. Providing
> support for buffered write path is in TODO list.
Ah, I thought you meant sync I/O versus async I/O. So do you mean that
the testing should use _direct_ I/O (bypassing the cache)?
>
> >
> > o I think the apportionment algorithm doesn't work consistently well
> > for writes.
> >
> > o I think there are problems with significant performance loss when
> > doing random I/Os.
>
> This concerns me. I had a quick look and as per your results, even with
> group_idle=0 you are seeing this regression. I guess this might be coming
> from the fact that we idle on sync-noidle workload per group and that
> idling becomes significant as number of groups increase.
>
> Thanks
> Vivek
next prev parent reply other threads:[~2009-11-16 21:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 20:51 [RFC] Block IO Controller V2 - some results Alan D. Brunelle
2009-11-16 21:14 ` Vivek Goyal
2009-11-16 21:32 ` Alan D. Brunelle [this message]
2009-11-16 21:37 ` Vivek Goyal
2009-11-16 22:18 ` Vivek Goyal
2009-11-17 12:38 ` Alan D. Brunelle
2009-11-17 14:14 ` Vivek Goyal
2009-11-17 16:17 ` Corrado Zoccolo
2009-11-17 16:40 ` Vivek Goyal
2009-11-17 17:30 ` Alan D. Brunelle
2009-11-17 17:44 ` Vivek Goyal
2009-11-17 20:59 ` Corrado Zoccolo
2009-11-17 22:38 ` Vivek Goyal
2009-11-17 23:11 ` Corrado Zoccolo
2009-11-19 0:04 ` Vivek Goyal
2009-11-19 20:12 ` Corrado Zoccolo
2009-11-17 16:45 ` Alan D. Brunelle
2009-11-18 15:32 ` Vivek Goyal
2009-11-18 16:20 ` Corrado Zoccolo
2009-11-18 22:56 ` Vivek Goyal
2009-11-18 23:35 ` Corrado Zoccolo
2009-11-20 14:18 ` Vivek Goyal
2009-11-20 14:28 ` Corrado Zoccolo
2009-11-20 15:04 ` Vivek Goyal
2009-11-20 18:32 ` Corrado Zoccolo
2009-11-20 18:42 ` Vivek Goyal
2009-11-20 19:50 ` Corrado Zoccolo
2009-11-21 17:57 ` Corrado Zoccolo
2009-11-23 15:19 ` Vivek Goyal
2009-11-23 16:22 ` Corrado Zoccolo
2009-11-17 20:38 ` Alan D. Brunelle
2009-11-19 16:57 ` 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=1258407135.3533.152.camel@cail \
--to=alan.brunelle@hp.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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