| To: | Bogdan Costescu <bogdan.costescu@xxxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] support for Cobalt Networks (x86 only) systems (forrealthis |
| From: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx> |
| Date: | Fri, 01 Jun 2001 09:15:37 -0400 |
| Cc: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Pete Zaitcev <zaitcev@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| Organization: | MandrakeSoft |
| References: | <Pine.LNX.4.33.0106011503030.18082-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
Bogdan Costescu wrote:
> No way! If I implement a HA application which depends on link status, I
> want the info to be accurate, I don't want to know that 30 seconds ago I
> had good link.
To tangent a little bit, and add netdev to the CC...
The loss and regain of link status should be proactively signalled to
userspace using netlink or something similar. Currently we have
netif_carrier_{on,off,ok} but it is only passively checked.
netif_carrier_{on,off} should probably schedule_task() to fire off a
netlink message...
For your HA application specifically, right now, I would suggest making
sure your net driver calls netif_carrier_xxx correctly, then checking
for IFF_RUNNING interface flag. IFF_RUNNING will disappear if the
interface is up, but there is no carrier [as according to
netif_carrier_ok].
--
Jeff Garzik | Disbelief, that's why you fail.
Building 1024 |
MandrakeSoft |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] ip_queue - netlink message handling oops fix, James Morris |
|---|---|
| Next by Date: | Re: [PATCH] support for Cobalt Networks (x86 only) systems (forrealthis, David S. Miller |
| Previous by Thread: | [PATCH] ip_queue - netlink message handling oops fix, James Morris |
| Next by Thread: | Re: [PATCH] support for Cobalt Networks (x86 only) systems (forrealthis, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |