Redirected from page "OPWIntro"

Clear message
  • Immutable Page
  • Info
  • Attachments

OutreachyIntro

Outreachy (formerly FOSS Outreach Program for Women (OPW) and Project Ascend Alumni)

Please see the Outreachy homepage for an introduction to the program.

Round 13 will be coming up in a few months. It's too early to send patches to the outreachy kernel mailing list, but please consider working through the other parts of the tutorial if you are intersted in applying.

We are looking for round 13 funding sponsors and Linux kernel mentors. Please see the linked FAQ pages if you want to help out.

Welcome Outreachy applicants! Our round 11 sponsors have generiously donated funds for internships for women, genderqueer, genderfluid, or genderfree people, and residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latino, American Indian, Alaska Native, Native Hawaiian, or Pacific Islander to work on the Linux kernel. The kernel is the most basic layer of the Linux operating system. It encompasses many things: hardware drivers, filesystems, security, task scheduling, and much more.

How to apply

The application period for Outreachy Round 12 is February 9 to March 22. Please fill your application by March 22, and complete your kernel patch by March 22 also (7pm UTC in both cases). Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our application FAQ for more info on how to fill out your application.

If you are interested in being a Linux kernel intern, please:

Participating Linux kernel projects

Applicants for all projects should have basic experience with C or C++ and boolean algebra. Optionally, we would love it if you have basic operating system knowledge, know your way around a Linux/UNIX command line, and/or know the revision system called git. Please note that these three skills can be learned during the internship.

Some projects may have small tasks you can complete as part of the application process. Do not start on these tasks until after you complete the first patch tutorial and Greg Kroah-Hartman has accepted at least ten of your cleanup patches and two of your patchsets. In order to ensure applicants aren't working on the same task, we need your help in coordinating who is working on what task. Please see the Outreachy tasks page for details before starting on a task!

Round 12 projects

Previous projects, from round 11 projects are available here. For each project, if you click on the proposer's name, you may find more information. The following is a partial list of projects. More will come soon.

Update legacy workqueue creation interface users

Mentor:: Tejun Heo

Workqueue is an asynchronous execution mechanism which is widely used across the kernel. A work item queued on a workqueue is asynchronously executed by a worker task (kworker/* in ps output). It's used for various purposes from simple context bouncing to hosting a persistent in-kernel service thread.

Due to its development history, there currently are two sets of interfaces to create workqueues.

  • create[_singlethread|_freezable]_workqueue()

  • alloc[_ordered]_workqueue()

The latter is the new interface which is superset of the former. While each create*_workqueue() can be directly mapped to an alloc*_workqueue() invocation, create*_workqueue() encodes much less information than alloc*_workqueue() making determining which exact flavor and attributes to use non-trivial. Each case should be examined to find out why a specific kind is used and then converted to an alloc*_workqueue() invocation which matches the requirements.

There currently are around 280 users of the legacy interface. While the number seems daunting, there are common patterns that many of them follow.

This project would involve understanding workqueue's various users to certain degree in addition to workqueue itself and can be a good opportunity to roam through and learn various parts of the kernel.

See the small tasks for this project on the mentor's page.

Coccinelle

Mentor:: Julia Lawall

Coccinelle is a program matching and transformation tool that has been extensively used for finding bugs in the Linux kernel. Around 50 Coccinelle rules are currently part of the kernel source code, and are regularly run on all kernel code changes via the 0-day build testing service. Still, there is the potential for many more such rules. The goal of this project is to prepare existing semantic patches, such as those found at coccinellery for inclusion in the kernel and to write some new ones. An optional part of the project could be to improve the coccinellery infrastructure, which is currently a 500 line bash script. Please indicate in your application whether you are interested in this part of the project, however, interest in this part of the project is not a prerequisite for being selected as an intern.

More information about Coccinelle is available here, including a tutorial. For some Coccinelle small tasks, click on the mentor name.

IIO driver

Mentor:: Daniel Baluta

A driver allows applications to communicate and control hardware devices. Each development cycle, driver changes account for more than a half of the total Linux kernel code changes.

The goal of this project is to write a driver for a sensor using the Industrial I/O interface. In the first part of the project you will get familiar with the hardware and the IIO subsystem then implement raw readings from the device. After upstreaming the code we will enhance the driver with support for buffered readings, power management and interrupts. The exact device will be decided when the internship starts.

We will provide you the hardware setup necessary to test the driver. If you are interested in this project please consider solving the IIO tasks.

nftables

Mentor:: Pablo Neira Ayuso

nftables provides a replacement for the very popular {ip,ip6,arp,eb}tables tools. nftables reuses most of the Netfilter components such as the existing hooks, connection tracking system, NAT, userspace queueing, logging among many other features. So we have only replaced the packet classification framework. nftables comes with a new userspace utility nft and the low-level userspace library libnftnl. The goal will be to help finish the translation layer software that converts from the iptables syntax to nftables, complete some simple missing features and fixing bugs whenever possible.

If you are interested in this project please consider solving any of the following tasks:

  • Request an account for the wiki.nftables.org page and help us improve the content.

  • Provide an iptables to nft translation via the iptables-translate utility. You can give a try to the following extensions: icmp, icmp6, rt.

  • Try to fix any of the existing nft bugs in bugzilla.netfilter.org.

For more information on nftables, please check: http://wiki.nftables.org

memory management latency tracing

Mentor: Rik van Riel

Every few months, some issue seems to pop up where users suffer from excessive latency at page fault and/or memory allocation time, usually (but not always) due to latency in the page reclaim code. Developers end up with some ad-hoc tracing to figure out the problem, because the kernel does not have a tool to discover the cause of these latencies on production systems. The goal of this project is to add the necessary tracepoints to the page fault, memory allocation, compaction, and reclaiming code, as well as some kind of script or tool in userspace that allows Linux users to obtain information on where time was spent when a memory allocation takes longer than a specified threshold.

This project requires learning about the memory management code, as well as tracepoints, and tracing tools in userspace.

See the small tasks for this project on the mentor's page.

Project

Mentor:: Mentor names

Brief project description.

Yeah, that sounds cool!

If you are interested in being a Linux kernel intern, please:

  • Join the outreachy-kernel mailing list

  • Join the #opw IRC channel on irc.gnome.org

  • Join the #kernel-outreachy IRC channel on irc.oftc.net

  • Read our instructions for applying, and apply by March 22.

  • Use our tutorial to send in your first kernel patch by March 22.

  • After you have sent several cleanup patches and at least one patchset, choose a small task to complete.

Tell others about this page:

last edited 2016-05-30 20:09:08 by JuliaLawall