Hello, On Wed, Apr 23, 2014 at 03:21:09PM -0400, Vivek Goyal wrote: > In general this idea makes sense. Exporting both request and bio will > solve the problem of io accounting. Also that should allow us to > get rid of blkio.io_merged. Yeah, that'd make more sense, I think. IO submitted vs. actually executed after merging. Pretty clear definition. > What about sync/async differentiation? Throttling layer seems to flag a request sync > only if bio->bi_rw flag has REQ_SYNC set. While CFQ seems to consider > request sync if bio is either read or bio->bi_rw has REQ_SYNC flag set. Heh, I think we'd need to unify those no matter what. The subtle difference is extremely confusing. > So we need to make this definition uniform. Or I am wondering do we > really need to export sync/async data. (Again put in by google folks). > How useful this info really is. Hmmmm... yeah, maybe that'd be the best way to go about it. 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
