From: Vivek Goyal <vgoyal@redhat.com>
To: Juerg Haefliger <juergh@gmail.com>
Cc: Heinz Mauelshagen <heinzm@redhat.com>, dm-devel@redhat.com
Subject: Re: [PATCH v2] dm-throttle: new device mapper target to throttle reads and writes
Date: Thu, 17 Mar 2011 09:15:42 -0400 [thread overview]
Message-ID: <20110317131542.GA32392@redhat.com> (raw)
In-Reply-To: <AANLkTimzzG6QvYD7V3M31J0U+jbB9GRXskzuw3aGhhCx@mail.gmail.com>
On Thu, Mar 17, 2011 at 12:01:06PM +0100, Juerg Haefliger wrote:
> > > FWIW, I am now playing with a RFC patch to implement device throttle mechanism
> > > on request queue instead of device mapper target and see how does it go. I am
> > > targetting to get the throtting limits from cgroups.
> > >
> > > The idea is to hook into __make_request and (ultimately dm_request) and
> > > subject incoming bios on request queue to throttling policy first before
> > > they are passed down to elevator.
> > >
> > > If it works, it should get rid of the requirement of configuring a device
> > > mapper target for throttling. At this point of time nothing is working and I
> > > am still figuring out how to put various pieces together.
> >
> > Ok, waiting for where that goes then.
>
> Is my understanding correct that dm-throttle has been abandoned in
> favor of the cgroups IO throttle controller?
Yes. Now throttling mechanism has been implemented in block layer which
is usable with the help of IO controller. So there is no need of a device
mapper target.
Thanks
Vivek
next prev parent reply other threads:[~2011-03-17 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 11:01 [PATCH v2] dm-throttle: new device mapper target to throttle reads and writes Juerg Haefliger
2011-03-17 13:15 ` Vivek Goyal [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-17 13:01 Heinz Mauelshagen
2010-08-17 13:16 ` Vivek Goyal
2010-08-17 13:35 ` Heinz Mauelshagen
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=20110317131542.GA32392@redhat.com \
--to=vgoyal@redhat.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@redhat.com \
--cc=juergh@gmail.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;
as well as URLs for NNTP newsgroup(s).