(no commit message)
[ikiwiki.git] / docs / developer / gsocprojectspage / index.mdwn
90c0b013 1[[!meta title="Google Summer of Code Project List"]]
4114eeff 2
3[[!toc levels=0]]
f57c228c 5Have a look at our SoC pages from [[2008|/docs/developer/GoogleSoC2008/]], [[2009|/docs/developer/gsoc2009/]], [[2010|/docs/developer/gsoc2010/]] and [[2011|/docs/developer/gsoc2011/]] to get an overview about prior year's projects.
4114eeff 6
7For more details on Google's Summer of Code: [Google's SoC page](http://socghop.appspot.com/)
f57c228c 9Alternate project links: [[Projects page|/docs/developer/ProjectsPage/]], [[Research Projects|/docs/developer/researchprojectspage/]]
4114eeff 11Note to prospective students: These project proposals are meant to be a first approximation; we're looking forward to your own suggestions (even for completely new directions) and will try to integrate your ideas to make the GSoC project more interesting to all parties. Even when a proposal is very specific about the goals that must be achieved and the path that should be taken, these are always negotiable. Keep in mind that we have tried to limit the proposals on this page to those that (based on our past experience) are appropriate for the GSoC program. This is by no means a comprehensive list, original ideas or proposals based on project ideas found on other pages are very welcome.
13Note to everyone else: These proposals are by no means Summer of Code specific, anyone is welcome and encouraged to adopt any of these projects at any time (just please let us know, or make a note on this page).
17* Prerequisites: knowledge that the student should have before starting the project. It may be possible to acquire the knowledge in the course of the project, but the estimated difficulty would increase substantially. On the bright side, you can expect to have a much deeper understanding of these fields (and gain some real-world experience) after you successfully complete the respective project.
18* Difficulty: Estimated difficulty of the project, taking into account the complexity of the task and the time constraints of the GSoC program.
19* Contact point: The person you should contact for any further information or clarifications. If the primary contact for a project does not respond in a reasonable amount of time (2-3 days), you should contact the appropriate DragonFly BSD mailing list, usually kernel@.
21#### Project ideas
a4c1e9f4 23##### Implement GEM for the DragonFly kernel
25The Graphics Execution Manager is a memory management system dedicated
26to Intel graphics chipsets. Along with KMS, it is a requirement of
272010 and more recent Intel Xorg drivers.
29The dports third-party application collection already contains all the userland bits needed to use the new drivers, provided WITH_NEW_XORG and WITH_KMS options are used in make.conf
31Background GEM information:
33* http://en.wikipedia.org/wiki/Graphics_Execution_Manager
34* http://lwn.net/Articles/283798/
35* http://blog.ffwll.ch/2012/10/i915gem-crashcourse.html
37Some kernel work has already been done in this domain by FreeBSD and could probably be adapted:
39* https://wiki.freebsd.org/Intel_GPU
41Related work has also been done previously by David Shao during a 2010 GSoC project:
43* http://www.dragonflybsd.org/docs/developer/GEMdrmKMS/
44* https://github.com/davshao/dflygsocdrm
46The dflygsocdrm branch is kept up-to-date but sadly seems to only be working on i386 DragonFly systems, and with ~2010 era Intel chipsets.
48An experimental port of the FreeBSD i915/kms code is also available, albeit non-working due to the missing GEM support.
50Adding PAT (Page Attribute Table) support to the kernel seems to be a required first step:
52* http://lwn.net/Articles/278994/
54Meta information:
56* Prerequisites: C, x86 architecture and paging knowledge
57* Difficulty: Moderate to difficult
58* Contact point: kernel@crater.dragonflybsd.org, #dragonfly irc channel
11f3d975 60---
316dbc40 62##### Implement GEM for the DragonFly kernel
64The Graphics Execution Manager is a memory management system dedicated
65to Intel graphics chipsets. Along with KMS, it is a requirement of
662010 and more recent Intel Xorg drivers.
68The dports third-party application collection already contains all the userland bits needed to use the new drivers, provided WITH_NEW_XORG and WITH_KMS options are used in make.conf
70Background GEM information:
72* http://en.wikipedia.org/wiki/Graphics_Execution_Manager
73* http://lwn.net/Articles/283798/
74* http://blog.ffwll.ch/2012/10/i915gem-crashcourse.html
76Some kernel work has already been done in this domain by FreeBSD and could probably be adapted:
78* https://wiki.freebsd.org/Intel_GPU
80Related work has also been done previously by David Shao during a 2010 GSoC project:
82* http://www.dragonflybsd.org/docs/developer/GEMdrmKMS/
83* https://github.com/davshao/dflygsocdrm
85The dflygsocdrm branch is kept up-to-date but sadly seems to only be working on i386 DragonFly systems, and with ~2010 era Intel chipsets.
87An experimental port of the FreeBSD i915/kms code is also available, albeit non-working due to the missing GEM support.
89Adding PAT (Page Attribute Table) support to the kernel seems to be a required first step:
91* http://lwn.net/Articles/278994/
93Meta information:
95* Prerequisites: C, x86 architecture and paging knowledge
96* Difficulty: Moderate to difficult
97* Contact point: kernel@crater.dragonflybsd.org, #dragonfly irc channel
b3634623 101##### Implement Linux compatibility for the x86_64 DragonFly kernel
102* Add a syscall table which translates Linux system calls to DragonFly ones
a6283272 103* Add support for ELF binary detection.
906b9635 105DragonFly/i386 supports the execution of 32 bit Linux binaries; it
106is only natural to implement the same kind of binary compatibility
107for 64-bit systems.
a6283272 108
906b9635 109Some of the other *BSD systems may already have implemented such a mechanism.
a6283272 110
111Meta information:
b3634623 113* Prerequisites: C, i386 and amd64 architecture knowledge
a6283272 114* Difficulty: Moderate to difficult
115* Contact point: kernel@crater.dragonflybsd.org
4114eeff 117---
01f0e620 119##### Sync DragonFly jail capability with FreeBSD jail capability
56852582 120* Implement sysctl -d security.jail.{param}> (see FreeBSD man 8 jail)
01f0e620 121* port libjail (jail(), jail_get(), jail_set(), jail_remove(), jail_attach() functions) and incorporate into base
122* remove jail(), jail_attach() functions from libC
123* update existing system jail tools: jail, jls, jexec to match FreeBSD functionality and to use libjail
51f0cdd6 125The DragonFly jails were updated from FreeBSD-4.8 capability to FreeBSD 5.1 capability in 2005. They haven't been improved on since. This goal of this project is to make DragonFly jails to be functionally identical to FreeBSD 9.x jail functionality such that software designed to work using modern FreeBSD jail functions will work on DragonFly without modification.
01f0e620 126
127Meta information:
129* Prerequisites: C, OS Internals
130* Difficulty: Moderate to difficult
131* Contact point: kernel@crater.dragonflybsd.org
4fcf3f2c 135##### Make allocation in the DragonFly kernel NUMA-aware
4114eeff 136
137* Parse related ACPI tables
138* NUMA-aware memory allocation
139* References:
140[ACPI SLIT parser](http://mail-index.netbsd.org/tech-kern/2009/11/23/msg006518.html)
141[ACPI SRAT parser](http://mail-index.netbsd.org/tech-kern/2009/11/23/msg006517.html)
142[NetBSD NUMA diff](http://www.netbsd.org/~cegger/numa2.diff)
143[NetBSD NUMA x86 diff](http://www.netbsd.org/~cegger/numa_x86.diff) (These patches now in NetBSD tree)
4fcf3f2c 145* This is a huge project, the initial GSoC portion of this project should focus only on creating infrastructure and proving out that infrastructure. The initial work should attempt to not create or enforce any specific allocation _policies_ based on the available NUMA information, simply provide that information in an easy to access and use fashion and create the possibility at various levels of implementing a future allocation policy. This could be initially proven out with simple dummy policies.
4114eeff 147Meta information:
149* Prerequisites: C, introductory computer architecture
a4c1e9f4 150* Difficulty: Easy-Hard
4114eeff 151* Contact point: kernel@crater.dragonflybsd.org
4114eeff 155##### Port valgrind to DragonFlyBSD
157Valgrind is a very useful tool on a system like DragonFly that's under heavy development. Since valgrind is very target specific, a student doing the port will have to get acquainted with many low level details of the system libraries and the user<->kernel interface (system calls, signal delivery, threading...). This is a project that should appeal to aspiring systems programmers. Ideally, we would want the port to be usable with vkernel processes, thus enabling complex checking of the core kernel code.
159The goal of this project is to port valgrind to the DragonFlyBSD platform so that at least the memcheck tool runs sufficiently well to be useful. This is in itself a challenging task. If time remains, the student should try to get at least a trivial valgrind tool to work on a vkernel process.
161Meta information:
163* Prerequisites: C, x86 assembly, low-level OS internals
164* Difficulty: Hard
165* Contact point: Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>
a4c1e9f4 169##### Make vkernels checkpointable
4114eeff 170
171* See checkpt(1).
172* Implement save and restore of segment registers so that threaded applications may be checkpointed. The segment registers support TLS. There are potential security concerns here.
173* Teach the checkpt system call how to checkpoint multiple vmspaces.
174* Add code to the vkernel which gets triggered upon reception of a SIGCKPT signal to dump/load e.g. the current state of network drivers.
175* This would allow us to save and restore or even migrate a complete DragonFly operating system running on the vkernel platform.
176This could be especially handy on laptops (if we'd get X11 operating in vkernels).
177* See also: http://www.dragonflybsd.org/docs/developer/CheckpointFeatures/
a4c1e9f4 178* A student made good progress on this in 2011, a future student could use her work as a foundation to stand on to complete the project: https://github.com/iriina/DragonFlyBSD/tree/test2.10.1
4114eeff 179
180Meta information:
182* Prerequisites: C, OS internals
183* Difficulty: Medium
184* Contact point: Michael Neumann <mneumann@ntecs.de>
185* References: [1](http://leaf.dragonflybsd.org/mailarchive/kernel/2007-02/msg00073.html) [2](http://leaf.dragonflybsd.org/mailarchive/users/2007-02/msg00034.html)
189##### HAMMER compression
191* Compress blocks as they get written to disk.
192* Only file data (rec_type == DATA) should be compressed, not meta-data.
193* the CRC should be that of the uncompressed data.
194* ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.
195* compression could be turned on a per-file or per-pfs basis.
196* gzip compression would be just fine at first.
198Doing compression would require flagging the data record as being compressed and also require double-buffering since
199the buffer cache buffer associated with the uncompressed data might have holes in it and otherwise referenced by user
200programs and cannot serve as a buffer for in-place compression or decompression.
202The direct read / direct write mechanic would almost certainly have to be disabled for compressed buffers and the
203small-data zone would probably have to be used (the large-data zone is designed only for use with 16K or 64K buffers).
205Meta information:
207* Prerequisites: C, filesystem internals
208* Difficulty: Difficult
209* Contact point: Michael Neumann <mneumann@ntecs.de>
4114eeff 213##### Userland System V Shared Memory / Semaphore / Message Queue implementation
214* Implement some or all of these subsystems in their entirety, or as completely as possible in userland using a daemon, mmap and the DragonFly umtx_sleep(2)/umtx_wakeup(2) or other userland facilities.
215* Any security or other major hurdles to this approach that would likely have to be implemented in-kernel should be noted in the students application.
216* Test and benchmark the new facilities with heavy SysV consumers such as PostgreSQL
217* Identify performance tradeoffs made in the userland implementation versus the existing kernel implementation. If time permits identify and apply solutions to these tradeoffs so that the userland implementation performs on par with or better than the kernel implementation.
219Meta information:
221* Prerequisites: C, x86 assembly
222* Difficulty: Moderate
223* Contact point: Samuel J. Greear <sjg@thesjg.com>
227##### Port Hyper-V Linux Integration components to DragonFly
228* Microsoft released a dual BSD/GPL version of their para-virtualized drivers (SCSI and Networking) for Linux.
229* This work would require porting the Linux VMBus (Microsoft's equivlalent to XenBus) and the corresponding SCSI (StorVSC) and networking (NetVSC) drivers to DragonFly.
230* References: [Sources](http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eee39325-898b-4522-9b4c-f4b5b9b64551) [Architecture Overview](http://port25.technet.com/archive/2009/07/22/introduction-to-the-linux-integration-components.aspx)
8e2bdf60 231
232Meta information:
234* Prerequisites: C, OS internals
235* Difficulty: Hard
236* Contact point: kernel@crater.dragonflybsd.org
8e2bdf60 237
8cb8502a 238---
240##### Implement more dm targets
241* Since we now have dm (device mapper) in DragonFly, it would be nice to make better use of it. Currently we have a relatively small number of useful targets (crypt, linear and striped).
242* Other targets should be implemented, in particular the mirror target would be of interest. Other ideas are welcome, too. Before applying for this please discuss the target of interest on the mailing list or with me directly.
c2cfaa23 243* There is a start of a journalled mirror target, if you want to attack soft mirroring; the problem is a lot more difficult than it seems at first, so talking on the mailing list or on IRC would be definitely worthwhile!
8cb8502a 244
245Meta information:
247* Prerequisites: C, OS internals
248* Difficulty: Medium
c2cfaa23 249* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>, Venkatesh Srinivas <vsrinivas@dragonflybsd.org>
8cb8502a 250
3a9e5de8 251---
253##### Implement a new unionfs
254* unionfs is a particularly useful pseudo-fs which allows to have an upper and a lower filesystem on a single mountpoint. The upper mountpoint is mostly transparent, so that the lower mountpoint is accessible.
3a9e5de8 255* A typical use case is mounting a tmpfs filesystem as the upper and a read-only FS as the lower mp. This way files can be edited transparently even on a RO filesystem without actually modifying it.
65d9da85 256* The current unionfs is completely broken as it relies on the whiteout VFS technique which is not supported by HAMMER. A new unionfs implementation should not rely on archaic methods such as whiteout.
3a9e5de8 257
258Meta information:
260* Prerequisites: C, OS internals, ideally some knowledge of the FreeBSD/DragonFly VFS
261* Difficulty: Medium
262* Contact point: kernel@crater.dragonflybsd.org
8e2bdf60 263
0c47d1e1 264---
266##### Improve compatibility of libdevattr with Linux' libudev
267* Our libdevattr has an API which is mostly compatible with Linux' libudev, but it is doubtful that any Linux application making use of libudev would run out of the box on DragonFly with libdevattr.
b515bc2d 268* The aim of this project is to identify the shortcomings of libdevattr and fix them so that some common libudev applications work with our libdevattr.
269* This might involve some kernel hacking to improve our kern_udev and definitely includes some grunt work of "tagging" subsystems with the kern_udev API.
270* Most of the work will be in userland, though, working on udevd and libdevattr.
0c47d1e1 271
272Meta information:
274* Prerequisites: C, familiarity with Linux' libudev would be a plus
275* Difficulty: Medium
276* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>
9792e675 280---
fc1a3138 282##### Implement further dsched disk scheduling policies (2011 Project: BFQ)
9792e675 283* dsched is a highly flexible disk scheduling framework which greatly minimizes the effort of writing disk scheduling policies.
284* Currently only dsched_fq, a fairly simple fair-queuing policy, and noop policies are implemented.
285* The aim of this project would be to implement at least another useful disk scheduling policy, preferably one that improves interactivity.
286* Other ideas are welcome.
1e4090b0 287* This is a great opportunity for CS students interested in scheduling problems to apply their theoretical knowledge.
9792e675 288
289Meta information:
291* Prerequisites: C, OS internals, familiarity with disk scheduling
292* Difficulty: Medium
293* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>
82d3efd3 295---
692141e4 297##### Implement hardware nested page table support for vkernels
82d3efd3 298* Various modern hardware supports virtualization extensions, including nested pagetables.
299* The DragonFly BSD vmspaces API, used to support vkernels, is effectively a software implementation of nested pagetables.
300* The goal of this project would be to add support for detection of the hardware features on AMD and Intel cpu's and alter the vmspace implementation to use hardware support when available.
302Meta information:
9792e675 303
82d3efd3 304* Prerequisites: C, x86 assembly, OS internals
305* Difficulty: Hard
306* Contact point: kernel@crater.dragonflybsd.org
8ff76619 308---
ec874e8b 310##### Access to ktr(4) buffers via shared memory
311Our event tracing system, ktr(4), records interesting events in per-cpu buffers that are printed out with ktrdump(8). Currently, ktrdump uses libkvm to access these buffers, which is suboptimal. One can allow a sufficiently-privileged userspace process to map those buffers read-only and access them directly. For bonus points, design an extensible, discoverable (think reflection) mechanism that provides fast access via shared memory to data structures that the kernel chooses to expose to userland.
313Meta information:
315* Prerequisites: C, OS internals
316* Difficulty: Medium
317* Contact point: kernel@crater.dragonflybsd.org, Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>
9376443d 319---
a4c1e9f4 320
9376443d 321##### nmalloc (libc malloc) measurements and performance work
323nmalloc is our libc memory allocator it is a slab-like allocator; it recently had some work done to add per-thread caches, but there is much more work that could be done. A project on this might characterize fragmentation, try out a number of techniques to improve per-thread caching and reduce the number of total syscalls, and see if any are worth applying.
325Possible things to work on:
326(thread caches)
327* The per-thread caches are fixed-size; at larger object sizes (say 4K), this can result in a lot of memory tied up. Perhaps they should scale their max size inversely to the object size.
329* The per-thread caches are filled one-at-a-time from free(). Perhaps the per-thread caches should be burst-filled.
331* Perhaps the per-thread caches should age items out
333(slab zone allocation)
334* zone_alloc() currently burst-allocates slab zones with the zone magazine held across a spinlock.
336* zone_free() holds the zone magazine lock around bzero()ing a slab zone header
338* zone_free() madvise()s one slab at a time; it'd be nice to madvise() runs of contiguous slabs
340* zone_free() madvise()s very readily (for every slab freed). Perhaps it should only madvise slabs that are idle for some time
342* zone_free() burst-frees slabs. Its not clear whether this is a good idea.
345* currently allocations > either 4k or 8k are forced directly to mmap(); this means that idle memory from free slabs cannot be used to service those allocations and that we do no caching for allocations > than that size. this is almost certainly a mistake.
347* we could use a small (embeddable) data structure that allows:
3481. efficient coalescing of adjacent mmap space for madvise
3492. efficient queries for vmem_alloc() (w/ alignment!)
3503. compact and doesn't use any space in the zone header (dirty/cold!)
3514. allows traversal in address order to fight fragmentation
3525. keep two such data structures (one for dirty pages, one for cold pages)
355* These are just ideas; there are many more things possible and many of these things need a lot of measurement to evaluate them. It'd be interesting to see if any of these are appropriate for it.
358* http://www.usenix.org/event/usenix01/bonwick.html
360A description of the Sun Solaris work on which the DragonFly allocator is based; use this as an overview, but do not take it as gospel for how the DFly allocator works.
362* http://leaf.dragonflybsd.org/~vsrinivas/jemalloc-tech-talk.ogv (Jason Evans tech talk about jemalloc, 1/2011)
364jemalloc is FreeBSD's and Firefox's (and NetBSD and GNASH and ...)'s malloc; in this tech talk, Jason Evans reviews how jemalloc works, how it has changed recently, and how it avoid fragmentation.
366* http://endeavour.zapto.org/src/malloc-thesis.pdf (Ayelet Wasik's thesis 'Features of a Multi-Threaded Memory Allocator')
368This thesis is an excellent overview of many techniques to reduce contention and the effects these techniques have on fragmentation.
370* Prerequisites: C, a taste of data structures
371* Difficulty: moderate
372* Contact point: Venkatesh Srinivas <me@endeavour.zapto.org>
01b524ba 374---
4c7e21d4 376##### Make DragonFly multiboot capable
377Adjust the DragonFly kernel to be multiboot (the specification) capable. In addition, add necessary code to grub2 to understand our disklabel64 and anything else we need to be able to use grub2 to multiboot DragonFly without any chainloading involved.
379Meta information:
381* Prerequisites: C, OS internals
382* Difficulty: Easy/Moderate
383* Contact point: Alex Hornung <alexh@dragonflybsd.org>
103f9a35 385---
a4c1e9f4 386
103f9a35 387##### Extend dsched framework to support jails
388Extend/modify the dsched framework to take into account jails and etc. instead of always allocating a 'tdio'. This would allow different process groupings (such as all processes in a jail) to be scheduled together. A new jail-specific policy would have to be written to support this, or an existing policy modified.
390Meta information:
392* Prerequisites: C, OS internals
393* Difficulty: Moderate
394* Contact point: kernel@lists.dragonflybsd.org, Samuel J. Greear <sjg@thesjg.com>, Alex Hornung <alexh@dragonflybsd.org>
1a9c0407 396---
2a10524a 397
398##### Implement i386 32-bit ABI for x86_64 64-bit kernel
399* Add a 32-bit syscall table which translates 32-bit
400 system calls to 64-bit.
401* Add support for 32 bit compatibility mode operation
402 and ELF binary detection.
404The idea here is to support the execution of 32 bit DragonFly binaries in 64 bit DragonFly environments, something numerous other operating systems have done. Several things must be done to support this. First, the appropriate control bits must be set to execute in 32-bit compatibility mode while in usermode instead of 64-bit mode. Second, when a system call is made from 32-bit mode a translation layer is needed to translate the system call into the 64-bit requivalent within the kernel. Third, the signal handler and trampoline code needs to operate on the 32-bit signal frame. Fourth, the 32 and 64 bit ELF loaders both have to be in the kernel at the same time, which may require some messing around with procedure names and include files since originally the source was designed to be one or the other.
406There are several hundred system calls which translates to a great deal of 'grunt work' when it comes time to actually do all the translations.
a4c1e9f4 408In 2012 a GSoC made reasonable progress on this project, a future GSoC student could pick up where he left off: http://gitweb.dragonflybsd.org/~ivan/dragonfly.git/shortlog/refs/heads/32bit_api_dirty_2
2a10524a 410Meta information:
412* Prerequisites: C
413* Difficulty: Difficult (lots of moving parts, particularly the trapframes)
414* Contact point: dillon
2a10524a 416---
418##### Adapt pkgsrc to create a package system with dependency independence.
a4c1e9f4 419* Create a set of tools (even better if it can be used like a library) that modifies how the pkgsrc packages are installed, allowing for the ability to upgrade individual packages, without stopping applications that depend on said packages from working. One method of achieving this is detailed at http://www.dragonflybsd.org/goals/#packages but other methods may be possible. PC-BSD have written a tool called PBI Builder which modifies FreeBSD ports for their dependency independence PBI system, this could be used as a starting point for the DragonFly BSD tools. Any attempt at this should leave room in the implementation to potentially work with other build systems, such as dports.
2a10524a 420
421Meta information:
423* Prerequisites: C
424* Difficulty: ?
425* Contact point: kernel@crater.dragonflybsd.org
2a10524a 427---
8d0fe716 428
a4c1e9f4 429##### Ability to execute Mach-O (OS X) binaries
2bb9dcbe 430This is a project for a student with something to prove, executing a binary touches a huge number of moving parts of a modern kernel. This project would entail adding or porting support for Mach-O binaries to the DragonFly BSD kernel. It would also involve adding an additional system call vector, like the Linux vector used for linux binary emulation. This is quite a large and complicated task and any proposal will be expected to be well-researched to reflect that. The ability to execute non-GUI binaries that make use of shared libraries should be the minimum to which such a project should aspire. OpenDarwin is available as a reference or to port relevant code from.
432Meta information:
434* Prerequisites: C, OS internals, binary file formats
435* Difficulty: Hard
436* Contact point: Samuel J. Greear <sjg@thesjg.com>
2bb9dcbe 438---
45e67a9e 439
2ca36c15 440##### Installer rework
441Upgrade/partially rewrite the installer to be much simpler to maintain. As part of reworking the installer, several functions scattered around in other base utils should be factored out into libraries that both the installer and the util it comes from can use, e.g.:
45e67a9e 442
443* partitioning (both GPT and MBR) should be factored out into two libraries, that the fdisk and the gpt tools use, but the installer can make use of, too.
444* disklabel32/64 functionality
445* adduser (and other user/group management)
2ca36c15 447The updated installer should then make use of all these new libraries and other ones that are already available (libcryptsetup, libluks, liblvm, libtcplay) to offer more advanced features.
45e67a9e 448
450Meta information:
452* Prerequisites: C
453* Difficulty: Moderate
454* Contact point: kernel@lists.dragonflybsd.org, Alex Hornung <alexh@dragonflybsd.org>
45e67a9e 456
a4c1e9f4 458---
459 (please add)