On 10/31/2012 08:57 PM, Tejun Heo wrote: > I have a patch queued to add ->pre_destroy() - different from > Glauber's in that it can't fail, so we'll have > > ->create() > ->post_create() > ->pre_destroy() > ->destroy() > > Where ->create() may fail but none other can. This is not the topic of this thread, but since you brought it: If you take a look at the description patch in the patch I sent, the problem I outlined is that at create time, we don't know anything about which will the css_id be - and I would like to avoid creating yet another index. Is there any way you would suggest of handling this ? Any chance of us allocating the css_id earlier then? _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
