<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.minix3.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.minix3.org/feed.php">
        <title>Wiki studentprojects</title>
        <description></description>
        <link>https://wiki.minix3.org/</link>
        <image rdf:resource="https://wiki.minix3.org/lib/tpl/minix3d/images/favicon.ico" />
       <dc:date>2026-04-30T05:33:04+0200</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:asynnetstack&amp;rev=1415778824&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:exceptionhandlingunification&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:fastsockets&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:loadawereness&amp;rev=1416226881&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:netmemprot&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:netsrvqueueing&amp;rev=1415778631&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:profiling&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:scalablenetworkstack&amp;rev=1415778550&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:shutdownprotocol&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=studentprojects:start&amp;rev=1425910886&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.minix3.org/lib/tpl/minix3d/images/favicon.ico">
        <title>Wiki</title>
        <link>https://wiki.minix3.org/</link>
        <url>https://wiki.minix3.org/lib/tpl/minix3d/images/favicon.ico</url>
    </image>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:asynnetstack&amp;rev=1415778824&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-12T08:53:44+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:asynnetstack</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:asynnetstack&amp;rev=1415778824&amp;do=diff</link>
        <description>Asynchronous network stack

Since the Minix VFS is fully asynchronous and the LwIP server supports the asynchronous protocol, we would like to extend the asynchronous communication to the network drivers. Although they use asynchronous send to communicate with the LwIP/inet servers, the protocol is mostly synchronous. However, we have a replacement for the senda() and recv() pair which, in contrast, has a very little overhead, can be used across multiple cores with even less overhead and allows …</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:exceptionhandlingunification&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:exceptionhandlingunification</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:exceptionhandlingunification&amp;rev=1415713928&amp;do=diff</link>
        <description>Exception handling unification

(possible project)

Minix uses several ad-hoc mechanisms/protocols to handle exceptions (e.g. pagefaults) and other events (e.g. timer ticks). Typically, this is based on first sending notification to the userspace process that should handle the event (the handler), which consequently request information from the kernel. Except interrupts everything happens because of the currently running process. Therefore it is possible for the kernel to generate message on beh…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:fastsockets&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:fastsockets</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:fastsockets&amp;rev=1415713928&amp;do=diff</link>
        <description>Fast sockets for a fast network stack

We have demonstrated that is is possible to exploit multicore architectures to implement a fast and reliable network stack (paper) To demonstrate its performance, we have implemented new sockets that allow applications to pass data quickly to the stack without kernel involvement (copying). However, this implementation is fairly primitive since the full posix-compliance require to tackle many challenges. On the other hand, our stack also provides slow socket…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:loadawereness&amp;rev=1416226881&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-17T13:21:21+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:loadawereness</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:loadawereness&amp;rev=1416226881&amp;do=diff</link>
        <description>Load aware effeective scheduler for multicore Minix

A master student implemented frequency scaling driver for our development platforms and evaluated and in-house LwIP based multi-component network stack, however, the benchmarked scenarios were configured statically. Our goal is to take this project farther and add a load aware scheduler which can dynamically scale frequencies of individual cores and migrate system processes between core so that we deliver the best performance required for the …</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:netmemprot&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:netmemprot</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:netmemprot&amp;rev=1415713928&amp;do=diff</link>
        <description>Efficient memory allocation and protection in a multicore network stack

We have implemented a new network stack in Minix 3, which is split into multiple servers and runs on multiple cores to improve performance of the original INET server by several orders of magnitude and to improve dependability of the stack by being able to update and recover from crashes of individual components of the stack. Crucial part of the design is passing data through the stack without copying. We have a basic imple…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:netsrvqueueing&amp;rev=1415778631&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-12T08:50:31+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:netsrvqueueing</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:netsrvqueueing&amp;rev=1415778631&amp;do=diff</link>
        <description>Reducing latency in Internet by improving buffering and feedback in the network stack

We have implemented a new network stack in Minix 3, which is split into multiple servers and runs on multiple cores to improve performance of the original INET server by several orders of magnitude and to improve dependability of the stack by being able to update and recover from crashes of individual components of the stack. On the other hand, the performance of such a stack is limited by the extra latency in…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:profiling&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:profiling</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:profiling&amp;rev=1415713928&amp;do=diff</link>
        <description>Profiling Minix

To debug and optimize a system, it is necessary to know what is going on inside. Goal of this project is to design and implement a framework for profiling Minix and to export data collected in various parts of the system to the user. Currently, we can statistically profile Minix on a single CPU. It needs to be extended to SMP. However, this just a single data point. It is necessary to know what components are communicating, how often and to log selected communication. For low le…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:scalablenetworkstack&amp;rev=1415778550&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-12T08:49:10+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:scalablenetworkstack</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:scalablenetworkstack&amp;rev=1415778550&amp;do=diff</link>
        <description>Scalable Network Stack

We have demonstrated that is is possible to exploit multicore architectures to implement a fast and reliable network stack (paper). However, the main problem is that we can only use one cpu/core for one component of the stack. Therefore, once a core gets overloaded, the stack does not scale further. The goal of this project is to find out, how can we scale beyond the sing-cpu bottle-neck. Is it possible to run multiple TCP components? Which one would an application use to…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:shutdownprotocol&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:shutdownprotocol</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:shutdownprotocol&amp;rev=1415713928&amp;do=diff</link>
        <description>Shutdown protocol

When Minix is shutting down PM broadcast a KILL signal to all processes. That is not the best way to do it as it is racy and requires many asynchronous messages between PM and VFS

The goal of this project is:

	*  separate killing POSIX processes from the rest of the system</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=studentprojects:start&amp;rev=1425910886&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-03-09T15:21:26+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>studentprojects:start</title>
        <link>https://wiki.minix3.org/doku.php?id=studentprojects:start&amp;rev=1425910886&amp;do=diff</link>
        <description>Student Projects

Within our ongoing research work on MINIX 3, we frequently have open subproblems that can be assigned to computer science students as term project (MSc or BSc), individual programming assignment (IPA), or operating system lab course replacement. A list of open projects can be found on this page.  If you're interested in any of the listed projects, please send an e-mail to the owner of the project to make an appointment.  The list below is just intended to give you an idea about…</description>
    </item>
</rdf:RDF>
