From a4c1e9f4899740f6e7efe0faf18c7d5467cae584 Mon Sep 17 00:00:00 2001 From: sjg Date: Wed, 6 Mar 2013 12:43:07 -0800 Subject: [PATCH] --- docs/developer/gsocprojectspage/index.mdwn | 155 +++++++-------------- 1 file changed, 48 insertions(+), 107 deletions(-) diff --git a/docs/developer/gsocprojectspage/index.mdwn b/docs/developer/gsocprojectspage/index.mdwn index 8646ee44..6d24cc67 100644 --- a/docs/developer/gsocprojectspage/index.mdwn +++ b/docs/developer/gsocprojectspage/index.mdwn @@ -20,6 +20,43 @@ Legend: #### Project ideas +##### Implement GEM for the DragonFly kernel + +The Graphics Execution Manager is a memory management system dedicated +to Intel graphics chipsets. Along with KMS, it is a requirement of +2010 and more recent Intel Xorg drivers. + +The 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 + +Background GEM information: + +* http://en.wikipedia.org/wiki/Graphics_Execution_Manager +* http://lwn.net/Articles/283798/ +* http://blog.ffwll.ch/2012/10/i915gem-crashcourse.html + +Some kernel work has already been done in this domain by FreeBSD and could probably be adapted: + +* https://wiki.freebsd.org/Intel_GPU + +Related work has also been done previously by David Shao during a 2010 GSoC project: + +* http://www.dragonflybsd.org/docs/developer/GEMdrmKMS/ +* https://github.com/davshao/dflygsocdrm + +The dflygsocdrm branch is kept up-to-date but sadly seems to only be working on i386 DragonFly systems, and with ~2010 era Intel chipsets. + +An experimental port of the FreeBSD i915/kms code is also available, albeit non-working due to the missing GEM support. + +Adding PAT (Page Attribute Table) support to the kernel seems to be a required first step: + +* http://lwn.net/Articles/278994/ + +Meta information: + +* Prerequisites: C, x86 architecture and paging knowledge +* Difficulty: Moderate to difficult +* Contact point: kernel@crater.dragonflybsd.org, #dragonfly irc channel + --- ##### Implement GEM for the DragonFly kernel @@ -71,8 +108,6 @@ for 64-bit systems. Some of the other *BSD systems may already have implemented such a mechanism. -Given Linux software available in pkgsrc and dports is i386 only at this date (2013-03-06), it would be more practical to avoid working on amd64 linux applications at first. - Meta information: * Prerequisites: C, i386 and amd64 architecture knowledge @@ -97,30 +132,6 @@ Meta information: --- -##### 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 allocation in the DragonFly kernel NUMA-aware * Parse related ACPI tables @@ -136,12 +147,11 @@ Meta information: Meta information: * Prerequisites: C, introductory computer architecture -* Difficulty: Easy +* Difficulty: Easy-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. @@ -156,7 +166,7 @@ Meta information: --- -##### Make vkernels checkpointable (2011 Project) +##### 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. @@ -165,6 +175,7 @@ Meta information: * 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/ +* 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 Meta information: @@ -213,31 +224,6 @@ Meta information: --- -##### 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. @@ -331,6 +317,7 @@ Meta information: * Contact point: kernel@crater.dragonflybsd.org, Aggelos Economopoulos --- + ##### nmalloc (libc malloc) measurements and performance work nmalloc 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. @@ -386,17 +373,6 @@ This thesis is an excellent overview of many techniques to reduce contention and --- -##### Create a filesystem indexing service -Currently to locate an arbitrary file on a dragonfly system you would use the locate(1), which(1) or whereis(1) tools. These are a bit clunky, paint in broad strokes and the accuracy of the database is often suspect. The first part of this project would involve implementing the Linux inotify interface in the DragonFly kernel. The second part would be to write a daemon that can (optionally) operate as an indexing service, if the weekly 310.locate periodic job see's that the locate database is being maintained by the daemon, it can skip running locate.updatedb(8). A third part of this project might involve extending the current database to a binary format with information about file types, what bits are set, etc. This could enable the user to have the locate tool paint in narrower strokes by specifying only files of type "ASCII text" or only files that are suid root or have the execute bit set. - -Meta information: - -* Prerequisites: C, OS internals, binary file formats -* Difficulty: Easy/Moderate -* Contact point: Samuel J. Greear - ---- - ##### Make DragonFly multiboot capable Adjust 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. @@ -407,6 +383,7 @@ Meta information: * Contact point: Alex Hornung --- + ##### Extend dsched framework to support jails Extend/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. @@ -417,24 +394,6 @@ Meta information: * Contact point: kernel@lists.dragonflybsd.org, Samuel J. Greear , Alex Hornung --- -##### Implement NFS version 4 -* NFSv4 is more than a simple version increase; it is an adaptation of NFS to Internet and WAN networks, with an expectation of high latency and firewalled data transfers and a non-naive security framework layer. -* NFSv4 servers export a single Pseudo File System (which has nothing to do with HAMMER(5) PFSes besides the name) merging all local filesystems in a unique namespace. -* We already have some kernel code which could be used as a starting point (WebNFS) -* FreeBSD possesses a NFSv4 implementation which could be ported or serve as a reference basis -* Given NFSv4 protocol complexity, it may be best to implement this project in userspace - -Meta information: - -* Prerequisites: C, OS internals, ideally some knowledge of the VFS and namecache layers -* Difficulty: Medium -* Contact point: kernel@crater.dragonflybsd.org - ---- - (please add) - - -## Old not-so-useful project ideas, don't look here ##### Implement i386 32-bit ABI for x86_64 64-bit kernel * Add a 32-bit syscall table which translates 32-bit @@ -446,23 +405,18 @@ The idea here is to support the execution of 32 bit DragonFly binaries in 64 bit 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. +In 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 + Meta information: * Prerequisites: C * Difficulty: Difficult (lots of moving parts, particularly the trapframes) * Contact point: dillon -Usefullness: - -DragonFly/x86_64 has been available for a few years, and is now -the most used DragonFly architecture. -There has never been an obvious need to use i386 DragonFly binaries -with it, all available DragonFly/i386 software can be rebuilt from source code. (comment added on 2013-02-21) - --- ##### 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. +* 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. Meta information: @@ -470,16 +424,9 @@ Meta information: * Difficulty: ? * Contact point: kernel@crater.dragonflybsd.org -Usefulness: - -A new dports/pkg packaging system based on FreeBSD ports and pkgng has -been implemented and is far superior to pkgsrc for all practical purposes. -Pkgsrc may not be the best base to start such a project and the time -needed to implement it will be far greater than the regular GSoc timeframe. More like one year than two months. (comment added on 2013-02-21) - --- -#####Ability to execute Mach-O (OS X) binaries +##### Ability to execute Mach-O (OS X) binaries This 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. Meta information: @@ -488,11 +435,6 @@ Meta information: * Difficulty: Hard * Contact point: Samuel J. Greear -Usefullness: - -This project will only allow us to execute a few command-line utilities, most of which are already present in all Unix like systems. -Beeing able to run Mac-OSX graphical applications will be a multi-year undertaking on top of it. Wine has been trying to reimplement Microsoft Windows APIs for 20 years already. (comment added on 2013-02-21) - --- ##### Installer rework @@ -511,8 +453,7 @@ Meta information: * Difficulty: Moderate * Contact point: kernel@lists.dragonflybsd.org, Alex Hornung -Usefulness: - -The current installer works well; it would be quicker and less dangerous to improve it instead of rewriting it entirely from scratch. (comment added on 2013-02-22) --- +--- + (please add) -- 2.41.0