> That's fair enough, though I think you'll find that the plain > project quota will find many different uses that filesystem > developers will have never thought of if it is there. e.g. I came > across an embedded NAS device a few years ago implemented with a > centralised object stores but had per-export space usage accounting > and enforcement by assigning every object associated with a specific > exported volume the same project quota.... 100% agreed. I can imagine that a lot of users will find their requirement of space managing with project quota. In this sense, general project quota is just like extended attribute comparing to internal attribute. For unknown use case in the future, I' d suggest to keep everything flexible. We don't really want to hear from customers that project quota looks attractive, but needs to be hacked to be usable for their usage. Regards, Li Xi -- 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
