(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]]
5Have a look at our SoC pages from [[2008|docs/developer/GoogleSoC2008/]], [[2009|docs/developer/gsoc2009]] and [[2010|docs/developer/gsoc2010]] to get an overview about prior year's projects.
7For more details on Google's Summer of Code: [Google's SoC page](http://socghop.appspot.com/)
9Note 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.
11Note 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).
15* 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.
16* Difficulty: Estimated difficulty of the project, taking into account the complexity of the task and the time constraints of the GSoC program.
17* 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@.
19#### Project ideas
21##### VFS Quota System
22* Create a new kernel subsystem to manage quota's in a filesystem agnostic manner by interfacing with the kernel VFS layer.
23* 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), ...).
24* 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.
26Meta information:
28* Prerequisites: C, introductory filesystems internals
29* Difficulty: Moderate
30* Contact point: Samuel J. Greear <sjg@thesjg.com>
4114eeff 34##### Implement i386 32-bit ABI for x86_64 64-bit kernel
35* Add a 32-bit syscall table which translates 32-bit
36 system calls to 64-bit.
37* Add support for 32 bit compatibility mode operation
38 and ELF binary detection.
40The 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.
42There are several hundred system calls which translates to a great deal of 'grunt work' when it comes time to actually do all the translations.
44Meta information:
46* Prerequisites: C
47* Difficulty: Difficult (lots of moving parts, particularly the trapframes)
48* Contact point: dillon
52##### Implement ARC algorithm extension for the vnode free list
53* Vnode recycling is LRU and can't efficiently handle data sets which
54 exceed the maxvnode limit. When the maxvnode limit is reached the kernel
55 starts throwing away cached vnodes along with their VM objects (and thus
56 all related cached file data).
58* What we would like to do is implement an ARC algorithm for the free
59 vnodes to determine which ones to throw away and potentially combine
60 this with further caching of the related VM object even after the vnode
61 is thrown away by associating it with a mount point and inode number,
62 until memory pressure forces all of its pages out.
64* For this project the student can choose to just implement the VM object
65 retention portion and not try to implement an ARC algorithm (which can
66 be considerably more complex).
68Meta information:
70* Prerequisites: C, OS internals
71* Difficulty: Modest without ARC (Very difficult with ARC)
72* Contact point: dillon
4114eeff 76##### Make DragonFly NUMA-aware
78* Parse related ACPI tables
79* NUMA-aware memory allocation
80* References:
81[ACPI SLIT parser](http://mail-index.netbsd.org/tech-kern/2009/11/23/msg006518.html)
82[ACPI SRAT parser](http://mail-index.netbsd.org/tech-kern/2009/11/23/msg006517.html)
83[NetBSD NUMA diff](http://www.netbsd.org/~cegger/numa2.diff)
84[NetBSD NUMA x86 diff](http://www.netbsd.org/~cegger/numa_x86.diff) (These patches now in NetBSD tree)
86Meta information:
88* Prerequisites: C, introductory computer architecture
89* Difficulty: Easy
90* Contact point: kernel@crater.dragonflybsd.org
95##### Port valgrind to DragonFlyBSD
97Valgrind 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.
99The 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.
101Meta information:
103* Prerequisites: C, x86 assembly, low-level OS internals
104* Difficulty: Hard
105* Contact point: Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>
109##### Adapt pkgsrc to create a package system with dependency independence.
110* 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.
112Meta information:
114* Prerequisites: C
115* Difficulty: ?
116* Contact point: kernel@crater.dragonflybsd.org
120##### Implement virtio drivers on DragonFly to speed up DragonFly as a KVM guest
122As virtualization is coming more and more and KVM will be a strong player in that field,
123we want DragonFly to have top-notch support for this virtualization platform. For this
124purpose, we'd like to have a virtio-based implementation of a paravirtualized disk and
125network driver. [virtio](http://www.ibm.com/developerworks/linux/library/l-virtio/index.html)
126is an abstraction to a ring buffer that is shared between the host and the guest. On top of this
127abstraction, one can build a variety of paravirtualized devices, as specified in
130The goal of this project is to create a virtio-ring implementation and then to implement drivers
131for the network and block devices described in the specification linked to above. This is a great
132project for a student who wants to get experience writing (real-world, high-performance) device
133drivers without having to deal with the quirks of real hardware.
135Meta information:
137* Prerequisites: C, elementary OS internals
138* Difficulty: Easy
139* Contact point: Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>, kernel@crater.dragonflybsd.org
143##### Port PUFFS from FreeBSD/NetBSD
145* http://www.netbsd.org/docs/puffs/
146* This would make many userspace filesystems available to DragonFly, e.g. sshfs to mention only one.
148Meta information:
150* Prerequisites: C, elementary OS internals
151* Difficulty: Medium
152* Contact point: Michael Neumann <mneumann@ntecs.de>
156##### Make vkernels checkpointable
158* See checkpt(1).
159* 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.
160* Teach the checkpt system call how to checkpoint multiple vmspaces.
161* 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.
162* This would allow us to save and restore or even migrate a complete DragonFly operating system running on the vkernel platform.
163This could be especially handy on laptops (if we'd get X11 operating in vkernels).
164* See also: http://www.dragonflybsd.org/docs/developer/CheckpointFeatures/
166Meta information:
168* Prerequisites: C, OS internals
169* Difficulty: Medium
170* Contact point: Michael Neumann <mneumann@ntecs.de>
171* References: [1](http://leaf.dragonflybsd.org/mailarchive/kernel/2007-02/msg00073.html) [2](http://leaf.dragonflybsd.org/mailarchive/users/2007-02/msg00034.html)
175##### HAMMER compression
177* Compress blocks as they get written to disk.
178* Only file data (rec_type == DATA) should be compressed, not meta-data.
179* the CRC should be that of the uncompressed data.
180* ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.
181* compression could be turned on a per-file or per-pfs basis.
182* gzip compression would be just fine at first.
184Doing compression would require flagging the data record as being compressed and also require double-buffering since
185the buffer cache buffer associated with the uncompressed data might have holes in it and otherwise referenced by user
186programs and cannot serve as a buffer for in-place compression or decompression.
188The direct read / direct write mechanic would almost certainly have to be disabled for compressed buffers and the
189small-data zone would probably have to be used (the large-data zone is designed only for use with 16K or 64K buffers).
191Meta information:
193* Prerequisites: C, filesystem internals
194* Difficulty: Difficult
195* Contact point: Michael Neumann <mneumann@ntecs.de>
200##### Port usb4bsd
201* Port the whole usb4bsd stuff to DragonFly, as our own usb stack is too outdated.
203* The usb4bsd branch of hselasky (?) has several userland wrappers and quite good abstraction to simplify the porting.
205Meta information:
207* Prerequisites: C, OS internals
208* Difficulty: Moderate
209* Contact point: kernel@crater.dragonflybsd.org
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>
228##### Update our interrupt routing and PCI code
229* Update our interrupt routing to ACPI interrupt routing instead of relying on the mptable exclusively
230* Update the PCI code to take advantage of MSI (Message Signalled Interrupts)
232Meta information:
234* Prerequisites: C, OS internals
235* Difficulty: Hard
236* Contact point: kernel@crater.dragonflybsd.org
2d009d1c 237* References: [1](http://people.freebsd.org/~jhb/papers/bsdcan/2007/article/article.html) [2](http://www.bsdcan.org/2007/schedule/events/2.en.html) [3](http://www.acpi.info/DOWNLOADS/ACPIspec40a.pdf) [4](http://tldp.org/LDP/tlk/dd/interrupts.html) [5](http://wiki.osdev.org/Category:Interrupts)
4114eeff 238
4114eeff 239---
8e2bdf60 241##### DragonFly history access for Gnome/KDE
5654e978 242* Write a Dolphin (KDE) plugin or Gnome file manager plugin that creates a 'time slider' when working with HAMMER filesystems.
243* If time remains investigate additional features and/or methods of display and possibly a HAMMER configuration utility for managing history retention, etc.
8e2bdf60 244
245Meta information:
5654e978 247* Prerequisites: C, Gnome or KDE familiarity
8e2bdf60 248* Difficulty: Hard
249* Contact point: kernel@crater.dragonflybsd.org
250* References: [A similar idea for ZFS](http://blogs.sun.com/erwann/entry/zfs_on_the_desktop_zfs)
254##### Create a Samba VFS plugin to expose Hammer history
255* Give access to Hammer snapshots/fine-grained history to anyone able to access the Hammer volume over Samba
5654e978 256* This would involve writing a Samba3 VFS module to expose historical versions of files as "shadow copies". VFS module implementations supporting more traditional snapshot hierarchies do already exist.
8e2bdf60 257
258Meta information:
5654e978 260* Prerequisites: C
261* Difficulty: Moderate
8e2bdf60 262* Contact point: kernel@crater.dragonflybsd.org
266##### Port Hyper-V Linux Integration components to DragonFly
267* Microsoft released a dual BSD/GPL version of their para-virtualized drivers (SCSI and Networking) for Linux.
268* This work would require porting the Linux VMBus (Microsoft's equivlalent to XenBus) and the corresponding SCSI (StorVSC) and networking (NetVSC) drivers to DragonFly.
269* 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 270
271Meta information:
273* Prerequisites: C, OS internals
274* Difficulty: Hard
275* Contact point: kernel@crater.dragonflybsd.org
8e2bdf60 276
8cb8502a 277---
279##### Implement more dm targets
280* 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).
281* 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 282* 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 283
284Meta information:
286* Prerequisites: C, OS internals
287* Difficulty: Medium
c2cfaa23 288* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>, Venkatesh Srinivas <vsrinivas@dragonflybsd.org>
8cb8502a 289
3a9e5de8 290---
292##### Implement a new unionfs
293* 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 294* 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.
3a9e5de8 295* The current unionfs is completely broken as it relies on the whiteout VFS technique which is not supported by HAMMER.
297Meta information:
299* Prerequisites: C, OS internals, ideally some knowledge of the FreeBSD/DragonFly VFS
300* Difficulty: Medium
301* Contact point: kernel@crater.dragonflybsd.org
8e2bdf60 302
0c47d1e1 303---
305##### Improve compatibility of libdevattr with Linux' libudev
306* 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 307* 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.
308* 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.
309* Most of the work will be in userland, though, working on udevd and libdevattr.
0c47d1e1 310
311Meta information:
313* Prerequisites: C, familiarity with Linux' libudev would be a plus
314* Difficulty: Medium
315* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>
9792e675 319---
321##### Implement further dsched disk scheduling policies
322* dsched is a highly flexible disk scheduling framework which greatly minimizes the effort of writing disk scheduling policies.
323* Currently only dsched_fq, a fairly simple fair-queuing policy, and noop policies are implemented.
324* The aim of this project would be to implement at least another useful disk scheduling policy, preferably one that improves interactivity.
325* Other ideas are welcome.
1e4090b0 326* This is a great opportunity for CS students interested in scheduling problems to apply their theoretical knowledge.
9792e675 327
328Meta information:
330* Prerequisites: C, OS internals, familiarity with disk scheduling
331* Difficulty: Medium
332* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>
82d3efd3 334---
692141e4 336##### Implement hardware nested page table support for vkernels
82d3efd3 337* Various modern hardware supports virtualization extensions, including nested pagetables.
338* The DragonFly BSD vmspaces API, used to support vkernels, is effectively a software implementation of nested pagetables.
339* 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.
341Meta information:
9792e675 342
82d3efd3 343* Prerequisites: C, x86 assembly, OS internals
344* Difficulty: Hard
345* Contact point: kernel@crater.dragonflybsd.org
4114eeff 348 (please add)