Just to clarify a couple of points: On 2/24/10 12:47 AM, Ben Kloosterman wrote: > The original post did not state whether it was the system object GC or > application GCs , I took it ( probably wrongly) as any GC.
The architecture of the CapROS kernel does not use garbage collection. For CapROS, this discussion applies only to application GC. > I know Eros and its descendents were based on > disk first storage for security but I'm seeing a lot of newer devices with > no or very little local storage KeyKOS, EROS, and CapROS page to persistent storage, for which I generally use the term "disk" although its geometry and medium may vary. This is done not for security, but for persistence and increased capacity. Non-persistent versions of EROS and CapROS have been envisioned, which do not do paging, but still have all the security properties of the object-capability model. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ CapROS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/capros-devel
