-DragonFly BSD is planning to participate (pending acceptance) in the Google Summer of Code program for 2010.

-

-

-Have a look at our SoC pages from [[2008|docs/developer/GoogleSoC2008/]] and [[2009|docs/developer/gsoc2009]] to get an overview about prior year's projects. The [Projects Page](/docs/developer/ProjectsPage/) is also a potential source of ideas.

+DragonFly BSD participated in the Google Summer of Code program for 2010.

+Have a look at our SoC pages from [[2008|docs/developer/GoogleSoC2008/]] and [[2009|docs/developer/gsoc2009]] to see an overview of prior year's projects.

For more details on Google's Summer of Code: [Google's SoC page](http://socghop.appspot.com/)

-Legend:

-

-* 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.

-* Difficulty: Estimated difficulty of the project, taking into account the complexity of the task and the time constraints of the GSoC program.

-* Contact point: The person you should contact for any further information or clarifications.

-

-#### Project ideas

-

-##### VFS Quota System

-* Create a new kernel subsystem to manage quota's in a filesystem agnostic manner by interfacing with the kernel VFS layer.

-* Create filesystem-agnostic quota support tools for userland that obtain information in the same manner as eg: du(1) instead of parsing the filesystem internals directly as the existing quota tools do (see quotacheck(8), repquota(8), edquota(8), ...).

-* The quota file storage can be modeled after the existing UFS code that does the same, but should use the more general bytes, files and/or directories metrics instead of the somewhat UFS-specific blocks and inodes.

-and 5). Additionally, it should be possible to keep an internal (i.e. part

-of the volume) log to speed up resyncing and parity checking. Implementing

-those features would be ideal, but is not required.

-

- The crypt target must allow for different ciphers and cipher parameters and

-should make use of our in-kernel crypto infrastructure. It is probably

-necessary to do the encryption asynchronously which will require extending

-the current infrastructure.

-

-Meta information:

-

-* Prerequisites: C, elementary OS internals

-* Difficulty: Medium

-* Contact point: Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>

-

----

-

-##### Make DragonflyBSD Tickless

-* By default, the clock cyclic fires at 100 Hz, regardless of whether or not any timeouts/callouts are scheduled to fire/expire. This is suboptimal from a power efficiency standpoint, as at least one of the system's CPUs never become quiescent/idle enough to be brought into a low power state.

-This work involves re-implementing the services presently provided by clock() in a tickless (or event based) fashion, eliminating the need for the system to "wake up", only to realize that there's nothing to do on an otherwise idle system.

-* http://hub.opensolaris.org/bin/view/Project+tickless/lbolt

-

-Meta information:

-

-* Prerequisites: C, OS internals

-* Difficulty: ?

-* Contact point: kernel@crater.dragonflybsd.org

-

----

-

-##### Make the DragonflyBSD Dispatcher Power-aware

-* CPU power management as it it implemented today is relatively isolated from the rest of the system. As such, it is forced to periodically poll to measure the utilization of the system's CPU resources.

-* This project extends the kernel's existing topology aware scheduling facility to bring "power domain" awareness to the dispatcher. With this awareness in place, the dispatcher can implement coalescence dispatching policy to consolidate utilization onto a smaller subset of CPU domains, freeing up other domains to be power managed. In addition to being domain aware, the dispatcher will also tend to prefer to utilize domains already running at higher power/performance states...this will increase the duration and extent to which domains can remain quiescent, improving the kernel's ability to take advantage of features like deep C-states. Because the dispatcher will track power domain utilization along the way, it can drive active domain state changes in an event driven fashion, eliminating the need for the CPUPM subsystem to poll.

-* http://hub.opensolaris.org/bin/view/Project+tesla/CPUPM

-

-Meta information:

-

-* Prerequisites: C

-* Difficulty: ?

-* Contact point: kernel@crater.dragonflybsd.org

-

----

-

-##### Port DragonFly to ARM platform

-

-Meta information:

-

-* Prerequisites: C, ARM assembly, x86 assembly

-* Difficulty: Extremely hard

-* Contact point: kernel@crater.dragonflybsd.org

-

----

-

-##### Port valgrind to DragonFlyBSD

-

-Valgrind 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.

-

-The 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.

-

-Meta information:

-

-* Prerequisites: C, x86 assembly, low-level OS internals

-* Difficulty: Hard

-* Contact point: Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>

-

----

-

-##### Adapt pkgsrc to create a package system with dependency independence.

-* Create a set of tools 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.

-

-Meta information:

-

-* Prerequisites: C

-* Difficulty: ?

-* Contact point: kernel@crater.dragonflybsd.org

-

----

-

-##### Implement virtio drivers on DragonFly to speed up DragonFly as a KVM guest

-* As virtualization is coming more and more and KVM will be a strong player in that field, it might be a good idea to be the first BSD to have a virtio implementation that enables us to run at a better speed in comparison to the other BSDs and maybe close to Linux on this virtualization platform.

-

-Meta information:

-

-* Prerequisites: C

-* Difficulty: ?

-* Contact point: kernel@crater.dragonflybsd.org

-

----

-

-##### Port FUSE or PUFFS from FreeBSD/NetBSD

-

-* http://www.netbsd.org/docs/puffs/

-* This would make many userspace filesystems available to DragonFly, e.g. sshfs to mention only one.

-

-Meta information:

-

-* Prerequisites: C, elementary OS internals

-* Difficulty: Medium

-* Contact point: Michael Neumann <mneumann@ntecs.de>

-

----

-

-##### Make vkernels checkpointable

-

-* See checkpt(1).

-* Teach the checkpt syscall how to checkpoint multiple vmspaces.

-* Add code to the vkernel which gets triggered on SIGCKPT to dump/load e.g. the current state of network drivers.

-* This would allow us to save and restore or even migrate a complete DragonFly operating system running on the vkernel platform.

-This could be especially handy on laptops (if we'd get X11 operating in vkernels).

-* 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.

-* 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.

-* Test and benchmark the new facilities with heavy SysV consumers such as PostgreSQL

-* 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.