| To: | "Cureington, Tony" <tony.cureington@xxxxxx> |
|---|---|
| Subject: | Re: [Bonding-devel] Re: Bonding driver unreliable under high CPU load |
| From: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx> |
| Date: | Tue, 17 Sep 2002 15:45:57 -0400 |
| Cc: | Andrew Morton <akpm@xxxxxxxxx>, Pascal Brisset <pascal.brisset-ml@xxxxxxxxxx>, bonding-devel@xxxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| Organization: | MandrakeSoft |
| References: | <72A87F7160C0994D8C5A36E2FDC227F502B3E70D@txnexc01.americas.cpqcorp.net> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 |
Cureington, Tony wrote:
Speaking of bonding, I wonder about the above code -- why do you return mii->val_out directly? AFAICS you should test BMSR_LSTATUS (a.k.a. 0x0004) and return MII_LINK_READY or zero -- not a bunch of random bits. The status word can certainly be non-zero even when link is absent. Also, a further question: do you have access to the slave struct net_device? If so, just test netif_carrier_ok(slave_dev) and avoid all that ioctl calling if it returns non-zero. Jeff |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Bonding-devel] Re: Bonding driver unreliable under high CPUload, Jay Vosburgh |
|---|---|
| Next by Date: | [Fwd: Info: NAPI performance at "low" loads], Andrew Morton |
| Previous by Thread: | RE: [Bonding-devel] Re: Bonding driver unreliable under high CPU load, Cureington, Tony |
| Next by Thread: | Re: [Bonding-devel] Re: Bonding driver unreliable under high CPUload, Andrew Morton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |