From: Vivek Goyal <vgoyal@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, nauman@google.com,
dpshah@google.com, guijianfeng@cn.fujitsu.com
Subject: Re: [RFC PATCH] Block device bio throttling support [V3]
Date: Thu, 16 Sep 2010 11:39:39 -0400 [thread overview]
Message-ID: <20100916153939.GC16147@redhat.com> (raw)
In-Reply-To: <4C91BDA5.2090308@kernel.dk>
On Thu, Sep 16, 2010 at 08:48:05AM +0200, Jens Axboe wrote:
> On 2010-09-15 23:06, Vivek Goyal wrote:
> > Hi,
> >
> > This is V3 of the bio throttling patches. Following are changes since V2.
> >
> > - Added the support for throttling in terms of IOPS (READ/WRITE). If one
> > specifies both bandwidth as well as IOPS rules on a device then IO is
> > subjected to both the rules.
> >
> > - Did few bug fixes.
> >
> > - Did some cleanups in blk-cgroup code.
>
> Vivek, I have merged these patches now to get some exposure and
> testing before .37 gets too close.
Thanks Jens.
Few things I had in mind.
- I have not implemented any barrier or ordering mechanism in throttling
logic. I am assuming that all the barrier work to get rid of ordering
semantics will also go in 2.6.37 and then we really should not need
to implement any ordering in throttling logic. So it should be a non-issue.
- All throttling logic can simply be disabled by setting
CONFIG_BLK_DEV_THROTTLING=n. It is already disabled by default. I will
do some performance testing on faster storage to see what is the cost
if CONFIG_BLK_DEV_THROTTLING=y and bandwidth is unlimited.
- I am still trying to figure out what to do about max number of bios which
can be throttled and pending and how to gel it well with request queue
congestion logic.
Thanks
Vivek
next prev parent reply other threads:[~2010-09-16 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 21:06 [RFC PATCH] Block device bio throttling support [V3] Vivek Goyal
2010-09-15 21:06 ` [PATCH 1/7] blk-cgroup: Kill the header printed at the start of blkio.weight_device file Vivek Goyal
2010-09-15 21:06 ` [PATCH 2/7] blk-cgroup: Prepare the base for supporting more than one IO control policies Vivek Goyal
2010-09-15 21:06 ` [PATCH 3/7] blk-cgroup: Introduce cgroup changes for throttling policy Vivek Goyal
2010-09-15 21:06 ` [PATCH 4/7] blkio: Core implementation of throttle policy Vivek Goyal
2010-09-15 21:06 ` [PATCH 5/7] blk-cgroup: cgroup changes for IOPS limit support Vivek Goyal
2010-09-15 21:06 ` [PATCH 6/7] blkio: Implementation of IOPS limit logic Vivek Goyal
2010-09-15 21:06 ` [PATCH 7/7] blkio: Documentation Update Vivek Goyal
2010-09-16 6:48 ` [RFC PATCH] Block device bio throttling support [V3] Jens Axboe
2010-09-16 15:39 ` Vivek Goyal [this message]
2010-09-16 7:10 ` Divyesh Shah
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=20100916153939.GC16147@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=dpshah@google.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nauman@google.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