Hi Christoph, > > I would appreciate it if you could take a look and review this patch > > and advice me about merging dm-ioband to upstream. > > Do we have any agreement on what io bandwith controller we want to > merge? Personally I don't think a dm target is a good idea, this seem > like something we want to tie into the block layer directly, especially > when using cfq so that it gets integrated into the scheduling decisions. I don't think the IO bandwidth controller has to be integrated into the IO scheduler, because I think there are many cases where people only want bandwidth control, no need to classify IOs like CFQ. I think a dm target is a very good idea for the following reasons: - A user have a choice whether to use dm-ioband or not, and dm-ioband doesn't make any effects on the system if a user doesn't use it. - The dm target is highly independent module, so we don't need to modify the existing kernel code including the IO schedulers. It can keep the IO scheduler and the IO bandwidth controller implementations simple. Thanks, Ryo Tsuruta -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
