Messages in this thread | | | Date | Wed, 18 Jul 2007 16:15:38 -0700 | From | "Paul Menage" <> | Subject | Re: Containers: css_put() dilemma |
| |
On 7/17/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote: > > Thinking out loud again, can we add can_destroy() callbacks? >
What would the exact semantics of such a callback be?
Since for proper interaction with release agents we need the subsystem to notify the framework when a subsystem object becomes releasable (currently as part of css_put()), what would a can_destroy() callback let you do that you couldn't do just by taking an extra css refcount to prevent destruction and releasing that refcount to allow destruction?
Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |