From: Stephen Hemminger <shemminger@osdl.org>
To: "Tadeusz Andrzej Kadłubowski" <yess@hell.org.pl>
Cc: zhangliang <liangzh@mail.bme.zju.edu.cn>, bridge@lists.osdl.org
Subject: Re: [Bridge] Re: Google SoC proposal (Tadeusz Andrzej Kad?ubowski)
Date: Mon, 8 May 2006 09:52:34 -0700 [thread overview]
Message-ID: <20060508095234.69a0b146@localhost.localdomain> (raw)
In-Reply-To: <20060508081547.GA21825@hell.org.pl>
On Mon, 8 May 2006 10:15:47 +0200
Tadeusz Andrzej Kadłubowski <yess@hell.org.pl> wrote:
> Thus wrote zhangliang:
> >
> > I think the prorosal is very good, I also want to do something for it, but
> > first we should have some more knowledge about rstp, Now what only I can do
> > is to read librstp, but I find that is so difficult to understand rstp, can
> > u give some more info about it?
>
> Apart from reading librstp (which is considered to be messy etc.) we have two
> main sources:
>
> a) The RSTP standard itself can be downloaded from the IEEE webpage for free.
> It's code-number is 802.1d. Don't be put off by it's technical language.
>
> b) RSTP is based on STP. We have a decent working STP implementation inside the
> Linux kernel - it can give a general idea of how to implement some parts of
> RSTP.
>
There was also a version of RSTP done for ucLinux that I archived at:
http://developer.osdl.org/shemminger/prototypes/rstp-2.4.zip
But, I don't want RSTP to be in the kernel.
prev parent reply other threads:[~2006-05-08 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200605071901.k47J09tJ014231@smtp.osdl.org>
2006-05-08 1:30 ` [Bridge] Re: Google SoC proposal (Tadeusz Andrzej Kad?ubowski) zhangliang
2006-05-08 8:15 ` Tadeusz Andrzej Kadłubowski
2006-05-08 16:52 ` Stephen Hemminger [this message]
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=20060508095234.69a0b146@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=liangzh@mail.bme.zju.edu.cn \
--cc=yess@hell.org.pl \
/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.