* [PATCH 001/002] de2104x: force correct order when writing to rx ring
@ 2009-02-07 21:30 Risto Suominen
2009-02-09 1:51 ` David Miller
0 siblings, 1 reply; 2+ messages in thread
From: Risto Suominen @ 2009-02-07 21:30 UTC (permalink / raw)
To: Jeff Garzik, lkml
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
DescOwn should not be set, thus allowing the chip to use the descriptor, before
everything else is set up correctly.
Signed-off-by: Risto Suominen <Risto.Suominen@gmail.com>
---
The testing is done on kernel version 2.6.18.
--- drivers/net/tulip/de2104x.c.org 2006-09-20 06:42:06.000000000 +0300
+++ drivers/net/tulip/de2104x.c 2009-02-07 15:04:04.000000000 +0200
@@ -465,13 +465,14 @@ static void de_rx (struct de_private *de
drop = 1;
rx_next:
- de->rx_ring[rx_tail].opts1 = cpu_to_le32(DescOwn);
if (rx_tail == (DE_RX_RING_SIZE - 1))
de->rx_ring[rx_tail].opts2 =
cpu_to_le32(RingEnd | de->rx_buf_sz);
else
de->rx_ring[rx_tail].opts2 = cpu_to_le32(de->rx_buf_sz);
de->rx_ring[rx_tail].addr1 = cpu_to_le32(mapping);
+ wmb();
+ de->rx_ring[rx_tail].opts1 = cpu_to_le32(DescOwn);
rx_tail = NEXT_RX(rx_tail);
}
[-- Attachment #2: de2104x-rx.patch --]
[-- Type: text/x-diff, Size: 850 bytes --]
DescOwn should not be set, thus allowing the chip to use the descriptor, before
everything else is set up correctly.
Signed-off-by: Risto Suominen <Risto.Suominen@gmail.com>
---
The testing is done on kernel version 2.6.18.
--- drivers/net/tulip/de2104x.c.org 2006-09-20 06:42:06.000000000 +0300
+++ drivers/net/tulip/de2104x.c 2009-02-07 15:04:04.000000000 +0200
@@ -465,13 +465,14 @@ static void de_rx (struct de_private *de
drop = 1;
rx_next:
- de->rx_ring[rx_tail].opts1 = cpu_to_le32(DescOwn);
if (rx_tail == (DE_RX_RING_SIZE - 1))
de->rx_ring[rx_tail].opts2 =
cpu_to_le32(RingEnd | de->rx_buf_sz);
else
de->rx_ring[rx_tail].opts2 = cpu_to_le32(de->rx_buf_sz);
de->rx_ring[rx_tail].addr1 = cpu_to_le32(mapping);
+ wmb();
+ de->rx_ring[rx_tail].opts1 = cpu_to_le32(DescOwn);
rx_tail = NEXT_RX(rx_tail);
}
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH 001/002] de2104x: force correct order when writing to rx ring
2009-02-07 21:30 [PATCH 001/002] de2104x: force correct order when writing to rx ring Risto Suominen
@ 2009-02-09 1:51 ` David Miller
0 siblings, 0 replies; 2+ messages in thread
From: David Miller @ 2009-02-09 1:51 UTC (permalink / raw)
To: risto.suominen; +Cc: jgarzik, linux-kernel
From: Risto Suominen <risto.suominen@gmail.com>
Date: Sat, 7 Feb 2009 23:30:24 +0200
> DescOwn should not be set, thus allowing the chip to use the descriptor, before
> everything else is set up correctly.
>
> Signed-off-by: Risto Suominen <Risto.Suominen@gmail.com>
Applied.
Please send networking patches to netdev@vger.kernel.org, especially
so that your patch gets properly logged and tracked at:
http://patchwork.ozlabs.org/project/netdev/list/
Thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-02-09 1:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-02-07 21:30 [PATCH 001/002] de2104x: force correct order when writing to rx ring Risto Suominen
2009-02-09 1:51 ` David Miller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).