On Tue, 2008-02-05 at 04:51 -0500, Oren Laadan wrote: > That said, I suggest the following method instead (this is the method > we use in Zap to determine the desired resource identifier when a new > resource is allocated; I recall that we had discussed it in the past, > perhaps the mini-summit in september ?): > > 1) The process/thread tells the kernel that it wishes to pre-determine > the resource identifier of a subsequent call (this can be done via a > new syscall, or by writing to /proc/self/...). > > 2) Each system call that allocates a resource and assigns an > identifier > is modified to check this per-thread field first; if it is set then > it will attempt to allocate that particular value (if already taken, > return an error, eg. EBUSY). Otherwise it will proceed as it is today.
You forgot to attach the patch to your mail. ;) -- Dave _______________________________________________ Containers mailing list [EMAIL PROTECTED] https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list Devel@openvz.org https://openvz.org/mailman/listinfo/devel
