| To: | Anton Blanchard <anton@xxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 2.6] e100: remove reference to NAPI config option |
| From: | Scott Feldman <sfeldma@xxxxxxxxx> |
| Date: | Mon, 31 Jan 2005 18:04:28 -0800 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20050201014358.GD15786@xxxxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <1107220952.3366.4.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20050201014358.GD15786@xxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | sfeldma@xxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Mon, 2005-01-31 at 17:43, Anton Blanchard wrote: > We have seen issues with NAPI on ppc64 on various cards in the past. > Its possibly due to missing memory barriers; the interrupt and read of > the interrupt status provide syncronization with DMA on the non NAPI > case. Without this you need to be very careful to order reads (eg > between reading the ring status and the packet data). Anton, do you think this is the same issue Russel King is reporting against ARM? http://marc.theaimsgroup.com/?l=linux-netdev&m=110686676829392&w=2 What happens in the ppc64 case? Do you have a fix for the ppc64 case? -scott |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 2.6] e100: remove reference to NAPI config option, Anton Blanchard |
|---|---|
| Previous by Thread: | Re: [PATCH 2.6] e100: remove reference to NAPI config option, Anton Blanchard |
| Indexes: | [Date] [Thread] [Top] [All Lists] |