From e1e29adceb071ca86c5a03a6c21c503e9a301f8d Mon Sep 17 00:00:00 2001 From: sjg Date: Wed, 1 Sep 2010 16:54:01 -0700 Subject: [PATCH] Remove research projects --- docs/developer/ProjectsPage.mdwn | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/docs/developer/ProjectsPage.mdwn b/docs/developer/ProjectsPage.mdwn index fa62443e..9557078f 100644 --- a/docs/developer/ProjectsPage.mdwn +++ b/docs/developer/ProjectsPage.mdwn @@ -145,32 +145,11 @@ This page shall serve as a common place to look if you're in search of a DragonF * Allow filesystems to define their own attribute vop ops * QUESTIONS: Attributes or subfiles? The consensus is that subfiles are better? -### Code generation hooks in the build system -* Well defined kernel build mechanisms for code generation -* This will require discussion - -### On-disk / Over-the-wire structure codegen -* Somewhat analogous to google protocol buffers / etc. -* Take a normalized definition of data, metadata, an operation and generate a structure, serialization routines and accessor routines for it/them -* Must be able to generate structs binary compatible with existing on-disk formats (including warts) -* Should magically create formats that are 32/64bit agnostic OR fixup serializers/unserializers -* Accessor routines and thread safety? Do we make you hang these objects somewhere that you store your synchronization objects or allow you to include them? -* Versioning? -* Potential uses: ... HAMMER, UFS, HAMMER mirror streams, message passing, ... -* QUESTIONS: Would people actually use them? - -### Asynchronous system call framework -* Probably best implemented as a message passing interface to kernel pass messages in, threads pick them up and execute, return through kevent notifications -* Would require a well-considered proposal - ### Hardware virtualization extensions * Increase performance of virtual kernels * Make use of hardware virtualization extensions, if supported, to manage vmspaces * Make use of hardware IOMMU support if available -### Kernel VIRTUAL MACHINE -* opcode vm in kernel for various purposes? What could be accomplished with this? - ### Remove zalloc * zalloc is a deprecated kernel interface and all current consumers can be ported to objcache, with varying levels of difficulty. * Easier: kqueue, nfs nodes, ufs dirhash, aio, crypto, vm_map_entry -- 2.41.0