On Tue, 2007-04-10 at 02:06 +0200, Patrick McHardy wrote: > Same way as the current RTM_SETLINK message works, but with creating > a new link in advance. It works fine in other subsystems, so I don't > see why it would in this case as well. Some subsystems do it in an > atomic fashion (network schedulers for example), some first create > the object, then configure it (network classifiers in the non-compat > cases). In the network device case I suppose the later should work > fine since a device needs to be set UP in a second action before > it really does anything. Our virtual devices are always associated with a piece of hardware, and we really want them to be associated with that at all times, even when not UP. Everything else seems like a huge complication if only because then we can't have whoever will be responsible for the device allocate it's private space area. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
