File:  [NetBSD Developer Wiki] / wikisrc / projects / project / policy_plugins.mdwn
Revision 1.1: download - view: text, annotated - select for diffs
Sun Nov 6 19:58:46 2011 UTC (2 years, 5 months ago) by jmmv
Branches: MAIN
CVS tags: HEAD
Add the projects from the website (htdocs/contrib/projects.xml).

At this point, all this is is a "blind conversion" from the xml file to
individual mdwn files.  I did this by using a custom xslt file and some
manual cleanups on the files.

Most of these projects are still misclassified as they do not list the
correct difficulty or the category they list is not yet defined in the
wiki.  Some other projects need to be pruned out due to the lack of
details (or moved to the ideas page).  But this is a "good enough" start
that should allow me to nuke these same projects from htdocs.

[[!template id=project

title="Installable cache control (or scheduling policies)"

contact="""
[tech-kern](mailto:tech-kern@NetBSD.org)
"""

category="kernel"
difficulty="medium"

description="""
The policy code in the kernel that controls file caching and readahead behavior
is necessarily one-size-fits-all, and the knobs available to applications to
tune it, like madvise() and posix_fadvise(), are fairly blunt
hammers. Furthermore, it has been shown that the overhead from user<->kernel
domain crossings makes syscall-driven fine-grained policy control ineffective.

Is it possible to create a BPF-like tool (that is, a small code generator with
very simple and very clear safety properties) to allow safe in-kernel
fine-grained policy control?

Caution: this is a research project.
"""
]]

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb