Hey, Vivek. On Mon, Jun 08, 2015 at 06:29:04PM -0400, Vivek Goyal wrote: ... > But above is not true for buffered writes, we will not associate io > context. Instead only cgroup information will be sent down and io > context of submitter will be used. > > So any thread which is forced to submit buffered write for some other > cgroup, will have its sync queue also reset (Because CFQ will think Yeah, it'll usually be the writeback work items. > that cgroup of submitter has changed). Not sure how often it will happen, > but if it happens frequenty, this might show up in profiles. I had They're unlikely to have sync queues associated with them to begin with and even when the context gets reset each iteration should be big enough to drown this sort of overhead. Writeback operates in a fairly sizable chunks. > mentioned this in the past and IIUC you said we will have to carry > writeback information all the way into lower layers. May be that's > an optimzation for later. So nothing new here, just trying to understand > the current situation. I'm actually kinda doubtful about caching async queues on cic at all. We already perform most of operations necessary to lookup the async queue for check_blkcg_changed(). We might as well just look up and pin each time. > Also I am wondring if this cgroup and io context information is carried > through dm layer or not. I guess it might be a separate discussion. It > has come for discussion internally in the past. So this might be a good > time to get attention of dm developers on these upcoming changes. (CC dm-devel). Hmmm... it depends on what dm does with the bio. It can surely propagate the cgroup information through sub bios. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
