All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tadeusz Andrzej Kadłubowski" <yess@hell.org.pl>
To: bridge@lists.osdl.org
Subject: [Bridge] Google SoC proposal
Date: Sat, 6 May 2006 19:54:14 +0200	[thread overview]
Message-ID: <20060506175414.GB11857@hell.org.pl> (raw)

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

Hello,

I am a student considering participating in Google Summer of Code program.

I came across Stephen Hemminger's idea of implementing a RSTP posted on
http://developer.osdl.org/dev/soc/ and found it interesting.

In attachment there's my proposal, which I just submitted to google.

Please share your comments.

-- 
tadeusz andrzej kadłubowski

[-- Attachment #2: zgl --]
[-- Type: text/plain, Size: 2936 bytes --]

			Linux RSTP implementation
			 Google SoC Application

Name:	Tadeusz Andrzej Kadłubowski
Email:  yess @ hell org pl
IRC:	yess @ freenode

The aim of this project is to create a Linux Rapid Spanning Tree
Protocol implementation as proposed by Mr Stephen Hemminger on
http://developer.osdl.org/dev/soc/

The system will be written in C and work as a daemon. It will be
configurable with a command line tool similar to brctl (probably a
modified brctl).

The tests will be a set of scripts - most likely perl or python unit
testing library will be used.

SCHEDULE OUTLINE
================

The project will take 13 weeks. We can assume 40 hours in a working
week.  My current duties occupy 2 days a week.

May:
	Reading and learning (IEEE standard, linux/net/core/,
	linux/net/bridge/, brctl sources, maybe documentation from UNH
	mentioned on http://developer.osdl.org/dev/soc/)
June:
	Messages from and to the kernel via rtnetlink interface
	Sending, receiving and parsing of BDPU messages
	Graph theory logic
	Exam in numerical mathematics will occupy my attention for 
	about a week. :|
July:
	State machine logic
	Timers
	User interface
	Framework for unit testing
	Numerous test units
August:
	Building scripts, packaging and release (if standalone)
	More documentation
	More testing
	
DELIVERABLES
============

* Linux RSTP daemon
* Command line tool to operate it
* Kernel bridge module patch in order to notify the userland (as
  needed)
* Set of test units
* Documentation (both for end-user and concerning inner structure)

MY USEFUL SKILLS
==============

* 6 years of C experience on Linux (with tools such as gdb, strace, vallgrind
  etc.)
* General idea of ,,Unix way of doing things'' and devotion for simplicity.
* Excellent understanding of graph theory, finite state automata and other
  necessary theoretical concepts.
* Some experience with low-level things (I took a small part in developing
  acpi4asus Linux driver having its main developer as a roommate)
* Enthusiasm for scripting languages (mostly python, bash and perl)

BIO + MOTIVATION
================

I'm a third year student at a CS faculty of the University of Gdańsk, Poland.
Having completed most of my courses on straight A's I feel perfectly capable
of completing this project.

I've been using Linux since '99. One of my computers operated as a STP-enabled
bridge in my high school network - that's where I learned basic networking
concepts. In those times I also learned C, which now I am perfectly familiar
with.

Recently I've completed third semester of Cisco CCNA course. This course gave
me insight into the world of embedded networking equipment and taught me a lot
about numerous aspects of networks. On the other hand their proprietary attitude
seemed odd and cumbersome to me. I started to see a great potential for
Linux-based networking equipment.


             reply	other threads:[~2006-05-06 17:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-06 17:54 Tadeusz Andrzej Kadłubowski [this message]
2006-05-06 23:57 ` [Bridge] Google SoC proposal Stephen Hemminger
2006-05-07 12:41   ` Tadeusz Andrzej Kadłubowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060506175414.GB11857@hell.org.pl \
    --to=yess@hell.org.pl \
    --cc=bridge@lists.osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.