Diff for /wikisrc/projects/project/policy_plugins.mdwn between versions 1.2 and 1.3

version 1.2, 2016/08/23 21:25:52 version 1.3, 2016/08/26 20:04:22
Line 1 Line 1
 [[!template id=project  [[!template id=project
   
 title="Installable cache control (or scheduling policies)"  title="Kernel plugins for FS policy logic (research)"
   
 contact="""  contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)  [tech-kern](mailto:tech-kern@NetBSD.org)
Line 15  is necessarily one-size-fits-all, and th Line 15  is necessarily one-size-fits-all, and th
 tune it, like madvise() and posix_fadvise(), are fairly blunt  tune it, like madvise() and posix_fadvise(), are fairly blunt
 hammers. Furthermore, it has been shown that the overhead from user<->kernel  hammers. Furthermore, it has been shown that the overhead from user<->kernel
 domain crossings makes syscall-driven fine-grained policy control ineffective.  domain crossings makes syscall-driven fine-grained policy control ineffective.
   (Though, that was shown in the past when processors were much slower
   relative to disks and it may not be true any more.)
   
 Is it possible to create a BPF-like tool (that is, a small code generator with  Is it possible to use BPF, or create a different BPF-like tool (that
   is, a small code generator with
 very simple and very clear safety properties) to allow safe in-kernel  very simple and very clear safety properties) to allow safe in-kernel
 fine-grained policy control?  fine-grained policy control?
   

Removed from v.1.2  
changed lines
  Added in v.1.3


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