Re: [PATCH v2] dm-throttle: new device mapper target to throttle reads and writes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel


[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux