add ktrdump-via-shared-memory project

[ikiwiki.git] / docs / developer / gsocprojectspage / index.mdwn

[[!meta title="Google Summer of Code Project List"]]

[[!toc levels=0]]

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

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

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

Note 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).

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

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

Meta information:

* Prerequisites: C, introductory filesystems internals
* Difficulty: Moderate
* Contact point: Samuel J. Greear <sjg@thesjg.com>

---

##### Implement i386 32-bit ABI for x86_64 64-bit kernel
* Add a 32-bit syscall table which translates 32-bit
  system calls to 64-bit.
* Add support for 32 bit compatibility mode operation
  and ELF binary detection.

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

There are several hundred system calls which translates to a great deal of 'grunt work' when it comes time to actually do all the translations.

Meta information:

* Prerequisites: C
* Difficulty: Difficult (lots of moving parts, particularly the trapframes)
* Contact point: dillon

---

##### Implement ARC algorithm extension for the vnode free list
* Vnode recycling is LRU and can't efficiently handle data sets which
  exceed the maxvnode limit.  When the maxvnode limit is reached the kernel
  starts throwing away cached vnodes along with their VM objects (and thus
  all related cached file data).

* What we would like to do is implement an ARC algorithm for the free
  vnodes to determine which ones to throw away and potentially combine
  this with further caching of the related VM object even after the vnode
  is thrown away by associating it with a mount point and inode number,
  until memory pressure forces all of its pages out.

* For this project the student can choose to just implement the VM object
  retention portion and not try to implement an ARC algorithm (which can
  be considerably more complex).

Meta information:

* Prerequisites: C, OS internals
* Difficulty: Modest without ARC (Very difficult with ARC)
* Contact point: dillon

---

##### Make DragonFly NUMA-aware 

* Parse related ACPI tables 
* NUMA-aware memory allocation
* References:
[ACPI SLIT parser](http://mail-index.netbsd.org/tech-kern/2009/11/23/msg006518.html)
[ACPI SRAT parser](http://mail-index.netbsd.org/tech-kern/2009/11/23/msg006517.html)
[NetBSD NUMA diff](http://www.netbsd.org/~cegger/numa2.diff)
[NetBSD NUMA x86 diff](http://www.netbsd.org/~cegger/numa_x86.diff) (These patches now in NetBSD tree)

Meta information:

* Prerequisites: C, introductory computer architecture
* Difficulty: Easy
* 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,
we want DragonFly to have top-notch support for this virtualization platform. For this
purpose, we'd like to have a virtio-based implementation of a paravirtualized disk and
network driver. [virtio](http://www.ibm.com/developerworks/linux/library/l-virtio/index.html)
is an abstraction to a ring buffer that is shared between the host and the guest. On top of this
abstraction, one can build a variety of paravirtualized devices, as specified in
[virtio-spec](http://ozlabs.org/~rusty/virtio-spec/virtio-spec-0.8.6.pdf).

The goal of this project is to create a virtio-ring implementation and then to implement drivers
for the network and block devices described in the specification linked to above. This is a great
project for a student who wants to get experience writing (real-world, high-performance) device
drivers without having to deal with the quirks of real hardware.

Meta information:

* Prerequisites: C, elementary OS internals
* Difficulty: Easy
* Contact point: Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>, kernel@crater.dragonflybsd.org

---

##### Port 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).
* 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.
* Teach the checkpt system call how to checkpoint multiple vmspaces.
* 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.
* 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).
* See also: http://www.dragonflybsd.org/docs/developer/CheckpointFeatures/

Meta information:

* Prerequisites: C, OS internals
* Difficulty: Medium
* Contact point: Michael Neumann <mneumann@ntecs.de>
* References: [1](http://leaf.dragonflybsd.org/mailarchive/kernel/2007-02/msg00073.html) [2](http://leaf.dragonflybsd.org/mailarchive/users/2007-02/msg00034.html)

---

##### HAMMER compression

* Compress blocks as they get written to disk.
* Only file data (rec_type == DATA) should be compressed, not meta-data.
* the CRC should be that of the uncompressed data.
* ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.
* compression could be turned on a per-file or per-pfs basis.
* gzip compression would be just fine at first.

Doing compression would require flagging the data record as being compressed and also require double-buffering since
the buffer cache buffer associated with the uncompressed data might have holes in it and otherwise referenced by user
programs and cannot serve as a buffer for in-place compression or decompression.

The direct read / direct write mechanic would almost certainly have to be disabled for compressed buffers and the
small-data zone would probably have to be used (the large-data zone is designed only for use with 16K or 64K buffers).

Meta information:

* Prerequisites: C, filesystem internals
* Difficulty: Difficult
* Contact point: Michael Neumann <mneumann@ntecs.de>

---


##### Port usb4bsd
* Port the whole usb4bsd stuff to DragonFly, as our own usb stack is too outdated.

* The usb4bsd branch of hselasky (?) has several userland wrappers and quite good abstraction to simplify the porting.

Meta information:

* Prerequisites: C, OS internals
* Difficulty: Moderate
* Contact point: kernel@crater.dragonflybsd.org

---

##### Userland System V Shared Memory / Semaphore / Message Queue implementation
* 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.

Meta information:

* Prerequisites: C, x86 assembly
* Difficulty: Moderate
* Contact point: Samuel J. Greear <sjg@thesjg.com>

---


##### Update our interrupt routing and PCI code
* Update our interrupt routing to ACPI interrupt routing instead of relying on the mptable exclusively
* Update the PCI code to take advantage of MSI (Message Signalled Interrupts)

Meta information:

* Prerequisites: C, OS internals 
* Difficulty: Hard
* Contact point: kernel@crater.dragonflybsd.org
* 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)

---

##### DragonFly history access for Gnome/KDE
* Write a Dolphin (KDE) plugin or Gnome file manager plugin that creates a 'time slider' when working with HAMMER filesystems.
* If time remains investigate additional features and/or methods of display and possibly a HAMMER configuration utility for managing history retention, etc.

Meta information:

* Prerequisites: C, Gnome or KDE familiarity
* Difficulty: Hard
* Contact point: kernel@crater.dragonflybsd.org
* References: [A similar idea for ZFS](http://blogs.sun.com/erwann/entry/zfs_on_the_desktop_zfs)

---

##### Create a Samba VFS plugin to expose Hammer history
* Give access to Hammer snapshots/fine-grained history to anyone able to access the Hammer volume over Samba
* 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.

Meta information:

* Prerequisites: C
* Difficulty: Moderate
* Contact point: kernel@crater.dragonflybsd.org

---

##### Port Hyper-V Linux Integration components to DragonFly
* Microsoft released a dual BSD/GPL version of their para-virtualized drivers (SCSI and Networking) for Linux.
* This work would require porting the Linux VMBus (Microsoft's equivlalent to XenBus) and the corresponding SCSI (StorVSC) and networking (NetVSC) drivers to DragonFly.
* 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)

Meta information:

* Prerequisites: C, OS internals
* Difficulty: Hard
* Contact point: kernel@crater.dragonflybsd.org

---

##### Implement more dm targets
* 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).
* 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.
* 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!

Meta information:

* Prerequisites: C, OS internals
* Difficulty: Medium
* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>, Venkatesh Srinivas <vsrinivas@dragonflybsd.org>

---

##### Implement a new unionfs
* 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.
* 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.
* The current unionfs is completely broken as it relies on the whiteout VFS technique which is not supported by HAMMER.

Meta information:

* Prerequisites: C, OS internals, ideally some knowledge of the FreeBSD/DragonFly VFS
* Difficulty: Medium
* Contact point: kernel@crater.dragonflybsd.org

---

##### Improve compatibility of libdevattr with Linux' libudev
* 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.
* 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.
* 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.
* Most of the work will be in userland, though, working on udevd and libdevattr.

Meta information:

* Prerequisites: C, familiarity with Linux' libudev would be a plus
* Difficulty: Medium
* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>



---

##### Implement further dsched disk scheduling policies
* dsched is a highly flexible disk scheduling framework which greatly minimizes the effort of writing disk scheduling policies.
* Currently only dsched_fq, a fairly simple fair-queuing policy, and noop policies are implemented.
* The aim of this project would be to implement at least another useful disk scheduling policy, preferably one that improves interactivity.
* Other ideas are welcome.
* This is a great opportunity for CS students interested in scheduling problems to apply their theoretical knowledge.

Meta information:

* Prerequisites: C, OS internals, familiarity with disk scheduling
* Difficulty: Medium
* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>

---

##### Implement hardware nested page table support for vkernels
* Various modern hardware supports virtualization extensions, including nested pagetables.
* The DragonFly BSD vmspaces API, used to support vkernels, is effectively a software implementation of nested pagetables.
* 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.

Meta information:

* Prerequisites: C, x86 assembly, OS internals
* Difficulty: Hard
* Contact point: kernel@crater.dragonflybsd.org

---

##### ATA TRIM and filesystem/swap support
* Some devices support an ATA command, 'TRIM', which marks disk blocks as 'not in use'; on SSDs, for example, not-in-use blocks can be used to support better wear leveling and to prevent performance degradation over time with fragmentation of the free block set.
* DFly's BIO system supports BIO_DELETE commands; these commands are not tied to device level TRIM commands, however
* Once BIO_DELETE commands are possible, it'd be very nice for DragonFly's swap code to generate BIO_DELETE commands for unused swap blocks (batch them!); this would would work well with SSDs and swapcache
* HAMMER should also send BIO_DELETE commands to mark unused blocks unused. Running HAMMER on an SSD would be more pleasant then.
* FreeBSD implemented this support on Jan 29th for UFS; it may serve as a good reference.

Meta information:

* Prerequisites: C, OS internals, a touch of file systems
* Difficult: Not too hard
* Contact point: kernel@crater.dragonflybsd.org

---

##### Access to ktr(4) buffers via shared memory
Our 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.

Meta information:

* Prerequisites: C, OS internals
* Difficulty: Medium
* Contact point: kernel@crater.dragonflybsd.org, Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>

---

 (please add)