[cap-talk] Another "core" principle - virtualize capabilities
Jonathan S. Shapiro
shap at eros-os.com
Thu Jan 4 14:24:11 CST 2007
On Thu, 2007-01-04 at 21:24 +0100, Marcus Brinkmann wrote:
> Let's start with the L4 mapping hierarchy model. In this case, there
> exists exactly one mapping tree per delegated resource. To allow for
> the above additional requirement, we would need to admit for a
> "cross-link" from the invoked capability to the fetched resource.
> The costs for this seems to be one additional pointer plus constant
> overhead per delegated resource. This would be accounted together
> with the other data from the delegation.
No. The cost of this is one additional pointer plust constant resource
**per transfer**. Every map operation in L4 allocates a resource in the
L4 mapping database.
Jonathan S. Shapiro, Ph.D.
The EROS Group, LLC
+1 443 927 1719 x5100
More information about the cap-talk