<div dir="ltr">On Sun, Sep 14, 2008 at 12:26 PM, Jonathan S. Shapiro <span dir="ltr"><<a href="mailto:shap@eros-os.com">shap@eros-os.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Finally, we have<br>
long since agreed that no feasible design exists for a transitively<br>
extended horton-style membrane in an OS-based capability system.<br>
</blockquote><div> </div></div>IIRC, the argument that horton is impractical in a OS-based ocap system is really: We have no good answers about who pays for the extra allocations or gets to reclaim that memory. In other list traffic, it seems like you're staring to consider OS design points which are somewhat sloppy on memory accounting issues. If the memory accounting constraints are relaxed, the horton question should be revisited.<br>
<br clear="all"><br>-- <br>Text by me above is hereby placed in the public domain<br><br> Cheers,<br> --MarkM<br><br>
</div>