(no commit message)
[ikiwiki.git] / docs / developer / ProjectsPage.mdwn
8c0cdf29 1# DragonFly Projects
b790f880 2
8c0cdf29 3This page shall serve as a common place to look if you're in search of a DragonFly related project. It's also the place to check if someone else is already working on it (to prevent project collision) or should be contacted.
b790f880 4
8c0cdf29 5[[!toc levels=3 ]]
b790f880 6
8c0cdf29 7## Website projects
b790f880 8
06d07101 9### One-liners
8753e704 10* Add traffic report, especially to lists requests that cause 404s
11* Add the mail archive to the search index
12* Download link right on the main page.
13* Fix [[RecentChanges]] page to have correct links back to git repo
14* Fix RSS feed to have correct links
15* Create layout for http://bugs.dragonflybsd.org that matches the main site.
16* Create short list of tasks for a new DragonFly user
17* how to upgrade the operating system
18* how to get to a working desktop
19* and where and how to report issues.
06d07101 20
21### Post papers in the proper locations on the website
8753e704 22* Format conversion may be necessary
23* Aggelos's papers from [http://leaf.dragonflybsd.org/~aggelos/] (http://leaf.dragonflybsd.org/~aggelos/) (netmp-paper.pdf and netmp.pdf) to Presentations
24* ["A Peek at the vKernel" article](http://cvsweb.dragonflybsd.org/cvsweb/site/data/docs/articles/vkernel/vkernel.shtml?rev=1.3&content-type=text/x-cvsweb-markup) from old site
b790f880 25
8c0cdf29 26## Documentation projects
b790f880 27
06d07101 28### One-liners
8753e704 29* Reorder `/usr/src/UPDATING` to put more relevant information at top; remove data no longer relevant.
30* Help out in [http://bugs.dragonflybsd.org](http://bugs.dragonflybsd.org) (try to reproduce, diagnose, propose fixes ...)
31* Organize, contribute to, and finish the C book project.
06d07101 32
33### Handbook maintenance
8753e704 34* Check if the content applies to DragonFly. If not, change it.
35* Add new content and enhance the previous chapters
36* Check for syntax error, typos and wiki errors.
37* Add prev/next buttons to all pages.
193c08af 38
8c0cdf29 39## Userland projects
b790f880 40
06d07101 41### One-liners
8753e704 42* Update the [[contributed software|docs/user/ContribSoftware]] which is out-of-date.
43* Remove `NOINET6` build option
44* `WARN` corrections to utilities
45* Bring in code from other *BSDs:
46* smbfs changes from FreeBSD
8753e704 47* Add extended slice support to `fdisk`
48* Install Coverity and fix the FreeBSD bugs that were uncovered by Coverity, but do not just blindly pull over the FreeBSD patches. Make sure that you first understand what the patch does.
49* C99 Standards Conformance. The todo list is on [[/docs/developer/StandardsConformanceProject]]
50* Setup a regression testing machine/system to register and find problems and new improvements..
51* Networking performance / scalability
52* [[RegressionTest|/docs/developer/RegressionTest]]
53* also check [[HowToStressTest|/docs/developer/HowToStressTest]]
54* Add lwp support to ptrace/gdb/core dumps.
55* [[/docs/developer/CheckpointFeatures]]
56* Linuxulator update (FreeBSD did a lot of work in this area. Look [here](http://wiki.freebsd.org/linux-kernel),
57* Bringing in version 2.0 of the BSD Installer
58* UTF8 support in the console
06d07101 59
60### Scalability (algorithmic performance)
8753e704 61* [http://bulk.fefe.de/scalability/](http://bulk.fefe.de/scalability/)
62* [http://bulk.fefe.de/lk2006/talk.pdf](http://bulk.fefe.de/lk2006/talk.pdf)
06d07101 63
06d07101 64### Clean our code to make it [style(9)](http://leaf.dragonflybsd.org/cgi/web-man?command#style&sectionANY) compatible.
8753e704 65* Compile and test your changes.
66* Verify that the checksum (sha(1)) of the unmodified object matches the checksum of the cleaned object. Check also with strip(1)+sha(1)
06d07101 67
68### Port BSD-licensed tools (ex: `grep`, `diff` and `sort`)
8753e704 69* The OpenBSD guys already did some work related to that.
70* If you manage to bring the tools to DragonFly, check if everything works as expected (e.g. rc.d scripts, make world runs, ...).
71* The new tools need to have at least all the features of the old GNU tools.
06d07101 72
73### Randomize mmap() offsets
8753e704 74* [http://www.openbsd.org/papers/ven05-deraadt/index.html](http://www.openbsd.org/papers/ven05-deraadt/index.html)
06d07101 75
99e24f21 76### GDB
8753e704 77* ptrace/gdb follow-fork-mode support and more (peek at linux)
78* Change the build to create one libbfd for gdb and binutils
79* Separate RPC code from NFS into separate library.
81### I/O diagnostic utilities
82* A utility similar to top which displays I/O usage on a per-process basis
83* Network, Disk
8c0cdf29 84
05f26292 85### SMART capabilities
86* Add to natacontrol (see NetBSD's atactl?)
87* Add to camcontrol
89### Disk scheduling rc scripts
90* Create a rc script to manage the disk/io scheduling system
91* Perhaps 1 entry to "enable" it, and all disks will have mode set to "auto", in auto mode smart inquiries and other heuristics could attempt to determine the best i/o scheduler
92* Per-device and device class or similar defaults should be definable in rc.conf also
dcf86f60 93* The bulk of this functionality could be implemented in a resurrected "dschedctl" utility and exposed through the rc interface using just a thin wrapper, allowing hotplug scripts and etc. an easier option to use the same facilities.
05f26292 94
8c0cdf29 95## Kernel projects
06d07101 97### One-liners
8753e704 98* Port the BSDL OSS code to DragonFly
99* Complete Path MTU Discovery by adding a host route to remember the Path MTU and setting a timer to expire old host routes. See netinet/if_ether.c for an example of this mechanism as used by ARP. Periodically increase MTU of hosts that have had its MTU decreased.
100* Look for places in the kernel that can benefit from Solaris-style caching of preconstructed slab allocator objects. If we can find enough of these uses, we can add this functionality to the kernel memory allocator.
101* Implement [`sem_open()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_open.html), [`sem_close()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_close.html), and [`sem_unlink()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_unlink.html).
102* Clean our code to make it [style(9)](http://leaf.dragonflybsd.org/cgi/web-man?command#style&sectionANY) compatible. Compile and test your changes. Verify that the checksum (sha(1)) of the unmodified object matches the checksum of the cleaned object. Check also with strip(1)+sha(1)
103* Setup a regression testing machine/system to register and find problems and new improvements..
104* Networking performance scalability
105* fix `APIC_IO` on SMP
106* Port or update drivers from other systems.
107* Port NFSv4. [This mail](http://leaf.dragonflybsd.org/mailarchive/kernel/2008-01/msg00065.html) is a good starting point.
8753e704 108* clean up buildworld/kernel compilation warnings
109* Port DragonFly over to Xen.
110* Port DTrace
111* Capriccio threads
06d07101 112
113### Code to port/sync from FreeBSD
8753e704 114* PCI code (to take advantage of power saving features)
8753e704 115* Bring in support for UFS2, just the changes to extend the width of some fields from 32 bits to 64 bits.
116* hardware drivers.
99e24f21 117
06d07101 118### Code to port/sync from OpenBSD
8753e704 119* Add support for the NoExecute bit as described in [http://www.openbsd.org/papers/auug04/index.html](http://www.openbsd.org/papers/auug04/index.html).
120* After that, make user stacks and data heaps non-executable. (W^X)
121* hardware drivers, specially wireless.
06d07101 122
df817d42 123### CPU scheduler
8753e704 124* A scheduler API supporting multiple scheduler implementations already exists
125* Add a Solaris-like dispatcher framework that can handle more than one installed scheduling policy
06d07101 126
127### I/O scheduler
df817d42 128* A pluggable kernel I/O scheduler already exists
129* Implement additional disk scheduling policies
8753e704 130
1ac22aa1 131### Modify firmware framework
132* We currently use the firmware(9) FreeBSD also uses
133* It would be more appropriate to avoid future problems with redistribution problems, etc, to adapt the wifi firmware stuff to use the firmware(9) we used to have before, which was able to load firmware files from userland (/etc/firmware).
134* See "firmware discussion" thread on kernel@ mailing list, March-May 2010.
ca622843 135* Since it's not desired to just add another way of doing it, this project should include getting rid of loading firmwares as modules
1ac22aa1 136
8753e704 137### Work relating to LWKT (LightWeightKernelThreading)
138* Implement lazy IPI cross-processor lwkt message passing.
139* Add timeout functionality to lwkt_waitmsg().
140* Write man pages for the lwkt message passing API.
142### Filesystem extended attributes
143* Generic VFS attributes layer
144* Emulate attributes ala Darwin
145* Allow filesystems to define their own attribute vop ops
146* QUESTIONS: Attributes or subfiles? The consensus is that subfiles are better?
148### Code generation hooks in the build system
149* Well defined kernel build mechanisms for code generation
150* This will require discussion
152### On-disk / Over-the-wire structure codegen
153* Somewhat analogous to google protocol buffers / etc.
154* Take a normalized definition of data, metadata, an operation and generate a structure, serialization routines and accessor routines for it/them
155* Must be able to generate structs binary compatible with existing on-disk formats (including warts)
156* Should magically create formats that are 32/64bit agnostic OR fixup serializers/unserializers
157* 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?
158* Versioning?
159* Potential uses: ... HAMMER, UFS, HAMMER mirror streams, message passing, ...
160* QUESTIONS: Would people actually use them?
162### Asynchronous system call framework
163* Probably best implemented as a message passing interface to kernel pass messages in, threads pick them up and execute, return through kevent notifications
164* Would require a well-considered proposal
166### Hardware virtualization extensions
167* Increase performance of virtual kernels
168* Make use of hardware virtualization extensions, if supported, to manage vmspaces
169* Make use of hardware IOMMU support if available
8753e704 171### Kernel VIRTUAL MACHINE
172* opcode vm in kernel for various purposes? What could be accomplished with this?