| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | RE: TG3 fix for slow switches (Was: TG3 driver failure on HP 16-way) |
| From: | "Michael Chan" <mchan@xxxxxxxxxxxx> |
| Date: | Thu, 23 Dec 2004 00:14:11 -0800 |
| Cc: | peterc@xxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| Thread-index: | AcToqUv3WYbMhI9bRy+/paHfI/WpywAHJSYb |
| Thread-topic: | TG3 fix for slow switches (Was: TG3 driver failure on HP 16-way) |
> Would this condition be possible if something, such as ASF, were > continually polling the PHY in parallel with the driver? Without proper handshake with ASF, I think it may be possible if ASF is in a very tight loop polling the PHY. The tg3_readphy() poll loop is not very tight so it is possible to continually hit the busy condition if ASF is polling PHY registers. If this is the case, even if tg3_readphy() eventually gets the data, the data will most likely be from a different PHY register (that ASF is trying to read). But I don't think this is an ASF related problem because if it were, the patch would not have fixed it. Michael |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | device driver problem, cranium2003 |
|---|---|
| Next by Date: | Re: LLTX and netif_stop_queue, Eric Lemoine |
| Previous by Thread: | Re: TG3 fix for slow switches (Was: TG3 driver failure on HP 16-way), David S. Miller |
| Next by Thread: | what is use of dev_queue_xmit_nit?, linux lover |
| Indexes: | [Date] [Thread] [Top] [All Lists] |