| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] (3/4) bridge linkstate handling |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 29 Jul 2004 08:12:44 -0400 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxx>, bridge@xxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040728162413.0de73ea3@dell_ss3.pdx.osdl.net> |
| Organization: | jamalopolis |
| References: | <20040728162413.0de73ea3@dell_ss3.pdx.osdl.net> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Wed, 2004-07-28 at 19:24, Stephen Hemminger wrote: > This makes bridge port status reflect both the state of the interface > from software (up/down) and the carrier. It makes STP handle link failure > (cable breakage, etc). The original concept comes from a > Mark Ruijter <bridge@xxxxxxxxxxx> who implemented it differently. > My way is simpler and requires no polling. > > Obviously, this link state detection will only work if the network card > handles the events properly. > nice. Does this entrench STP further in the kernel? Still planning to move it out to user space? cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [NET] Allow MD5 to be a module, Herbert Xu |
|---|---|
| Next by Date: | Re: [PATCH] kill rtnl_exlock stubs, Jamal Hadi Salim |
| Previous by Thread: | [PATCH] (3/4) bridge linkstate handling, Stephen Hemminger |
| Next by Thread: | Re: [PATCH] (3/4) bridge linkstate handling, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |