diff options
Diffstat (limited to 'microkernel')
| -rw-r--r-- | microkernel/viengoos.mdwn | 1 | ||||
| -rw-r--r-- | microkernel/viengoos/documentation.mdwn | 55 |
2 files changed, 56 insertions, 0 deletions
diff --git a/microkernel/viengoos.mdwn b/microkernel/viengoos.mdwn index 6b36e95c..09043719 100644 --- a/microkernel/viengoos.mdwn +++ b/microkernel/viengoos.mdwn @@ -21,4 +21,5 @@ check it out using, for example: * Running * [[QEMU]] * [[Hardware]] + * [[Documentation]] * [[Projects]] diff --git a/microkernel/viengoos/documentation.mdwn b/microkernel/viengoos/documentation.mdwn new file mode 100644 index 00000000..d7af9632 --- /dev/null +++ b/microkernel/viengoos/documentation.mdwn @@ -0,0 +1,55 @@ +[[meta copyright="Copyright © 2008 Free Software Foundation, Inc."]] + +[[meta license="""[[toggle id="license" text="GFDL 1.2+"]][[toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled +[[GNU_Free_Documentation_License|/fdl]]."]]"""]] + +The most up-to-date documentation is in the source code itself. The +second best are the header files. Look in particular in the hurd +directory to understand the Viengoos API. + +There is a started but as-of-yet incomplete manual in the doc +directory, which documents the Viengoos API and the Hurd API. + +Academic Papers: + + * [Viengoos: A Framework for Stakeholder-Directed Resource + Allocation](http://walfield.org/papers/2009-walfield-viengoos-a-framework-for-stakeholder-directed-resource-allocation.pdf). By + Neal H. Walfield. Submitted to EuroSys 2009. + +General-purpose operating systems not only fail to provide adaptive +applications the information they need to intelligently adapt, but +also schedule resources in such a way that were applications to +aggressively adapt, resources would be inappropriately scheduled. The +problem is that these systems use demand as the primary indicator of +utility, which is a poor indicator of utility for adaptive +applications. + +We present a resource management framework appropriate for traditional +as well as adaptive applications. The primary difference from current +schedulers is the use of stakeholder preferences in addition to +demand. We also show how to revoke memory, compute the amount of +memory available to each principal, and account shared +memory. Finally, we introduce a prototype system, Viengoos, and +present some benchmarks that demonstrate that it can efficiently +support multiple aggressively adaptive applications simultaneously. + + * [Improving Usability via Access Decomposition and Policy + Refinement with Marcus + Brinkmann](http://walfield.org/papers/20070104-walfield-access-decomposition-policy-refinement.pdf). By + Neal H. Walfield and Marcus Brinkmann. Technical report + (submitted to HotOS 2007). + +Commodity operating systems fail to meet the security, resource +management and integration expectations of users. We propose a unified +solution based on a capability framework as it supports fine grained +objects, straightforward access propagation and virtualizable +interfaces and explore how to improve resource use via access +decomposition and policy refinement with minimum interposition. We +argue that only a small static number of scheduling policies are +needed in practice and advocate hierarchical policy specification and +central realization. |