Scribit Bas Wijnen dies 23/04/2006 hora 00:31: > > > > 1. This requires dynamic storage allocation in the kernel. [...] > > > Can you elaborate why you think that dynamic storage allocation is > > > required? > > You stated that "simply dropping the capability [does not remove the > > obligation]". In order to satisfy this requirement, the kernel must > > keep track of every reply capability that a service ever receives. > This can be done in the capability structure itself, which is paid for > by the owner, not by the object or the kernel.
That depends on how the capabilities are implemented. I didn't read how Coyotos, L4.sec and L4ng do, but if the kernel allocates space when a capability is created, and only keeps references of it when it is passed between subjects, then the capability structure can't contain that information. Doubtfully, Nowhere man -- [EMAIL PROTECTED] OpenPGP 0xD9D50D8A
signature.asc
Description: Digital signature
_______________________________________________ L4-hurd mailing list [email protected] http://lists.gnu.org/mailman/listinfo/l4-hurd
