On Fri, Sep 14, 2012 at 12:44:39PM -0700, Tejun Heo wrote: > I think there currently is too much (broken) flexibility and intent to > remove it. That doesn't mean that removeing all flexibility is the > right direction. It inherently is a balancing act and I think the > proposed solution is a reasonable tradeoff. There's important > difference between causing full overhead by default for all users and > requiring some overhead when the use case at hand calls for the > functionality.
That said, if someone can think of a better solution, I'm all ears. One thing that *has* to be maintained is that it should be able to tag a resource in such way that its associated controllers are identifiable regardless of which task is looking at it. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
