On Wed, Feb 24, 2010 at 7:30 PM, William Leslie <
[email protected]> wrote:
> Letting the application developer decide the paging strategy makes
> memory pressure a more useful covert channel, though.
Not correct. What creates the channel is allowing the memory pressure of one
application to have impact on the paging behavior of a second application.
If this is sufficiently isolated, there is no further hazard from allowing
the application to make its own eviction choice.
The more I have looked at this class of "covert channel by policy leakage"
question, the less solvable I think they are. Bill went on to talk about
safe languages. In practice, this sort of cross-app policy is *critical*. If
you can cooperate about when the semi-space flip happens in the generational
collector, then the system needs only n+1 semispaces, where n is the number
of process. Otherwise it needs 2n. That's quite a large difference in memory
requirement...
shap
------------------------------------------------------------------------------
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
