From: Tejun Heo <tj@kernel.org>
To: Robin Dong <sanbai@taobao.com>
Cc: linux-kernel@vger.kernel.org, Zhu Yanhai <gaoyang.zyh@taobao.com>,
Vivek Goyal <vgoyal@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Tao Ma <taoma.tm@gmail.com>,
kent.overstreet@gmail.com
Subject: Re: [RFC v1] add new io-scheduler to use cgroup on high-speed device
Date: Tue, 4 Jun 2013 20:03:37 -0700 [thread overview]
Message-ID: <20130605030337.GO14916@htj.dyndns.org> (raw)
In-Reply-To: <1370398171-25173-1-git-send-email-sanbai@taobao.com>
(cc'ing Kent. Original posting at
http://thread.gmane.org/gmane.linux.kernel/1502484 )
Hello,
On Wed, Jun 05, 2013 at 10:09:31AM +0800, Robin Dong wrote:
> We want to use blkio.cgroup on high-speed device (like fusionio) for our mysql clusters.
> After testing different io-scheduler, we found that cfq is too slow and deadline can't run on cgroup.
> So we developed a new io-scheduler: tpps (Tiny Parallel Proportion Scheduler).It dispatch requests
> only by using their individual weight and total weight (proportion) therefore it's simply and efficient.
>
> Test case: fusionio card, 4 cgroups, iodepth-512
So, while I understand the intention behind it, I'm not sure a
separate io-sched for this is what we want. Kent and Jens have been
thinking about this lately so they'll probably chime in. From my POV,
I see a few largish issues.
* It has to be scalable with relatively large scale SMP / NUMA
configurations. It better integrate with blk-mq support currently
being brewed.
* It definitely has to support hierarchy. Nothing which doesn't
support full hierarchy can be added to cgroup at this point.
* We already have separate implementations in blk-throtl and
cfq-iosched. Maybe it's too late and too different for cfq-iosched
given that it's primarily targeted at disks, but I wonder whether we
can make blk-throtl generic and scalable enough to cover all other
use cases.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-06-05 3:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 2:09 Robin Dong
2013-06-05 3:03 ` Tejun Heo [this message]
2013-06-05 3:26 ` sanbai
2013-06-05 13:55 ` Vivek Goyal
2013-06-05 17:36 ` Tejun Heo
2013-06-05 13:59 ` Vivek Goyal
2013-06-05 13:30 ` Vivek Goyal
2013-06-07 3:09 ` sanbai
2013-06-07 19:53 ` Vivek Goyal
2013-06-08 3:50 ` sanbai
2013-06-08 4:38 ` sanbai
2013-06-05 2:23 Robin Dong
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=20130605030337.GO14916@htj.dyndns.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=gaoyang.zyh@taobao.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sanbai@taobao.com \
--cc=taoma.tm@gmail.com \
--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
all inboxes | Powered by JetHome®