On Thu, 2014-01-02 at 12:10 -0500, tj+AEA-kernel.org wrote: +AD4- Hey, Vivek. +AD4- +AD4- On Thu, Jan 02, 2014 at 12:06:37PM -0500, Vivek Goyal wrote: +AD4- +AD4- So is this a separate configuration which can be done per bdi as opposed +AD4- +AD4- to per device? IOW throttling offered per per cgroup per bdi. This will +AD4- +AD4- help with the case of throttling over NFS too, which some people have +AD4- +AD4- been asking for. +AD4- +AD4- Hah? No, bdi just being split per-cgroup on each device so that it can +AD4- properly propagate congestion upwards per-blkcg, just like how we +AD4- split request allocation per-cgroup in the block layer proper. +AD4- I'm not entirely sure how well this will fit with the filesystems (who already expect a single BDI), but it's worth trying. I'm definitely worried about having too many blkcgs and over-committing the dirty memory limits. BDI-per device setup we have now already has that problem, but I'm not sure its a good idea to make it worse. +AD4- +AD4- So it sounds like re-implementing throttling infrastructure at bdi level +AD4- +AD4- now (Similar to what has been done at device level)? Of course use as +AD4- +AD4- much code as possible. But IIUC, proposal is that effectively there will +AD4- +AD4- can be two throttling controllers. One operating at bdi level and one +AD4- +AD4- operating below it at device level? +AD4- +AD4- Not at all. I was arguing explicitly against that. Keep in mind that we do already have throttling at the BDI level. I was definitely hoping we could consolidate some of that since it has grown some bits of an elevator already. I'm not saying what we have in the bdi throttling isn't reasonable, but it is definitely replicating some of the infrastructure down below. We'll (Josef, me, perhaps others at FB) will do some experiments before LSF. The current plan is to throw some code at the wall and see what sticks. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
