Fix e100 on systems that have cache incoherent DMA
Subsystems (2)
PATCH 1/1 Fix e100 on systems that have cache incoherent DMA
On the systems that have cache incoherent DMA, including ARM, there is a race condition between software allocating a new receive buffer and hardware writing into a buffer. The two race on touching the last Receive Frame Descriptor (RFD). It has its el-bit set and its next link equal to 0. When hardware encounters this buffer it attempts to write data to it and then update Status Word bits and Actual Count in the RFD. At the same time software may try to clear the el-bit and set the link address to a new buffer.
Since the entire RFD is once cache-line, the two write operations can collide. This can lead to the receive unit stalling or interpreting random memory as its receive area.
The fix is to set the el-bit on and the size to 0 on the next to last buffer in the chain. When the hardware encounters this buffer it stops and does not write to it at all. The hardware issues an RNR interrupt with the receive unit in the No Resources state. Software can write to the tail of the list because it knows hardware will stop on the previous descriptor that was marked as the end of list.
Once it has a new next to last buffer prepared, it can clear the el-bit and set the size on the previous one. The race on this buffer is safe since the link already points to a valid next buffer and the software can handle the race setting the size (assuming aligned 16 bit writes are atomic with respect to the DMA read). If the hardware sees the el-bit cleared without the size set, it will move on to the next buffer and skip this one. If it sees the size set but the el-bit still set, it will complete that buffer and then RNR interrupt and wait.
Flags are kept in the software descriptor to note if the el bit is set and if the size was 0. When software clears the RFD's el bit and set its size, it also clears the el flag but leaves the size was 0 bit set. This way software can identify them when the race may have occurred when cleaning the ring. On these descriptors, it looks ahead and if the next one is complete then hardware must have skipped the current one. Logic is added to prevent two packets in a row being marked while the receiver is running to avoid running in lockstep with the hardware and thereby limiting the required lookahead.
This is a patch for 2.6.23-rc4.
---
drivers/net/e100.c renamed from drivers/net/e100.c.orig +136 -47
@@ -106,6 +106,13 @@* the RFD, the RFD must be dma_sync'ed to maintain a consistent * view from software and hardware. * +* In order to keep updates to the RFD link field from colliding with +* hardware writes to mark packets complete, we use the feature that +* hardware will not write to a size 0 descriptor and mark the previous +* packet as end-of-list (EL). After updating the link, we remove EL +* and only then restore the size such that hardware may use the +* previous-to-end RFD. +* * Under typical operation, the receive unit (RU) is start once, * and the controller happily fills RFDs as frames arrive. If * replacement RFDs cannot be allocated, or the RU goes non-active,
@@ -281,14 +288,14 @@ struct csr { };enum scb_status { + rus_no_res =0x08 , rus_ready =0x10 , rus_mask =0x3C , };enum ru_state { -RU_SUSPENDED =0 , -RU_RUNNING =1 , -RU_UNINITIALIZED =-1 , + ru_stopped =0 , + ru_running =1 , };enum scb_stat_ack {
@@ -401,10 +408,16 @@ struct rfd {u16 size; }; +enum rx_flags { + rx_el =0x01 , + rx_s0 =0x02 , +}; +struct rx {struct rx *next, *prev;struct sk_buff *skb;dma_addr_t dma_addr; +u8 flags; };#if defined(__BIG_ENDIAN_BITFIELD)
@@ -952,7 +965,7 @@ static void e100_get_defaults(struct nic ((nic->mac >= mac_82558_D101_A4) ? cb_cid : cb_i));/* Template for a freshly allocated RFD */ - nic->blank_rfd.command =cpu_to_le16 (cb_el); + nic->blank_rfd.command =0 ; nic->blank_rfd.rbd =0xFFFFFFFF ; nic->blank_rfd.size =cpu_to_le16 (VLAN_ETH_FRAME_LEN );
@@ -1753,18 +1766,48 @@ static int e100_alloc_cbs(struct nic *nireturn 0 ; } -static inline void e100_start_receiver (struct nic *nic,struct rx *rx) +static void e100_find_mark_el (struct nic *nic,struct rx *marked_rx,int is_running) { -if (!nic->rxs)return ; -if (RU_SUSPENDED != nic->ru_running)return ; +struct rx *rx = nic->rx_to_use->prev->prev; +struct rfd *rfd; + +if (marked_rx == rx) +return ; + + rfd = (struct rfd *) rx->skb->data; + rfd->command |=cpu_to_le16 (cb_el); + rfd->size =0 ; +pci_dma_sync_single_for_device (nic->pdev, rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); + rx->flags |= (rx_el | rx_s0); + +if (!marked_rx) +return ; + + rfd = (struct rfd *) marked_rx->skb->data; + rfd->command &= ~cpu_to_le16 (cb_el); +pci_dma_sync_single_for_device (nic->pdev, marked_rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); + + rfd->size =cpu_to_le16 (VLAN_ETH_FRAME_LEN ); +pci_dma_sync_single_for_device (nic->pdev, marked_rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); -/* handle init time starts */ -if (!rx) rx = nic->rxs; +if (is_running) + marked_rx->flags &= ~rx_el; +else + marked_rx->flags &= ~(rx_el | rx_s0); +} + +static inline void e100_start_receiver (struct nic *nic) +{ +if (!nic->rxs)return ; +if (ru_stopped != nic->ru_running)return ;/* (Re)start RU if suspended or idle and RFA is non-NULL */ -if (rx->skb) { -e100_exec_cmd (nic, ruc_start, rx->dma_addr); - nic->ru_running =RU_RUNNING ; +if (nic->rx_to_clean->skb) { +e100_exec_cmd (nic, ruc_start, nic->rx_to_clean->dma_addr); + nic->ru_running = ru_running; } }
@@ -1793,8 +1836,6 @@ static int e100_rx_alloc_skb(struct nicstruct rfd *prev_rfd = (struct rfd *)rx->prev->skb->data;put_unaligned (cpu_to_le32 (rx->dma_addr), (u32 *)&prev_rfd->link); -wmb (); - prev_rfd->command &= ~cpu_to_le16 (cb_el);pci_dma_sync_single_for_device (nic->pdev, rx->prev->dma_addr,sizeof (struct rfd ),PCI_DMA_TODEVICE ); }
@@ -1808,6 +1849,7 @@ static int e100_rx_indicate(struct nic *struct sk_buff *skb = rx->skb;struct rfd *rfd = (struct rfd *)skb->data;u16 rfd_status, actual_size; +u8 status;if (unlikely (work_done && *work_done >= work_to_do))return -EAGAIN ;
@@ -1819,9 +1861,47 @@ static int e100_rx_indicate(struct nic *DPRINTK (RX_STATUS ,DEBUG ,"status=0x%04X\n" , rfd_status); -/* If data isn't ready, nothing to indicate */ -if (unlikely (!(rfd_status & cb_complete))) +/* +* If data isn't ready, nothing to indicate +* If both the el and s0 rx flags are set, we have hit the marked +* buffer but we don't know if hardware has seen it so we check +* the status. +* If only the s0 flag is set, we check the next buffer. +* If it is complete, we know that hardware saw the rfd el bit +* get cleared but did not see the rfd size get set so it +* skipped this buffer. We just return 0 and look at the +* next buffer. +* If only the s0 flag is set but the next buffer is +* not complete, we cleared the el flag as hardware +* hit this buffer. +*/ +if (unlikely (!(rfd_status & cb_complete))) { +u8 maskedFlags = rx->flags & (rx_el | rx_s0); +if (maskedFlags == (rx_el | rx_s0)) { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + }else if (maskedFlags == rx_s0) { +struct rx *next_rx = rx->next; +struct rfd *next_rfd = (struct rfd *)next_rx->skb->data; +pci_dma_sync_single_for_cpu (nic->pdev, + next_rx->dma_addr,sizeof (struct rfd ), +PCI_DMA_FROMDEVICE ); +if (next_rfd->status &cpu_to_le16 (cb_complete)) { +pci_unmap_single (nic->pdev, rx->dma_addr, +RFD_BUF_LEN ,PCI_DMA_FROMDEVICE ); +dev_kfree_skb_any (skb); + rx->skb =NULL ; + rx->flags &= ~rx_s0; +return 0 ; + }else { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + } + }return -ENODATA ; + }/* Get actual data size */ actual_size =le16_to_cpu (rfd->actual_size) &0x3FFF ;
@@ -1832,9 +1912,15 @@ static int e100_rx_indicate(struct nic *pci_unmap_single (nic->pdev, rx->dma_addr,RFD_BUF_LEN ,PCI_DMA_FROMDEVICE ); -/* this allows for a fast restart without re-enabling interrupts */ -if (le16_to_cpu (rfd->command) & cb_el) - nic->ru_running =RU_SUSPENDED ; +/* +* This happens when hardward sees the rfd el flag set +* but then sees the rfd size set as well +*/ +if (le16_to_cpu (rfd->command) & cb_el) { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + }/* Pull off the RFD and put the actual data (minus eth hdr) */ skb_reserve (skb,sizeof (struct rfd ));
@@ -1865,32 +1951,34 @@ static int e100_rx_indicate(struct nic *static void e100_rx_clean (struct nic *nic,unsigned int *work_done,unsigned int work_to_do) { -struct rx *rx; +struct rx *rx, *marked_rx;int restart_required =0 ; -struct rx *rx_to_start =NULL ; - -/* are we already rnr? then pay attention!!! this ensures that -* the state machine progression never allows a start with a -* partially cleaned list, avoiding a race between hardware -* and rx_to_clean when in NAPI mode */ -if (RU_SUSPENDED == nic->ru_running) - restart_required =1 ; +int err =0 ;/* Indicate newly arrived packets */ for (rx = nic->rx_to_clean; rx->skb; rx = nic->rx_to_clean = rx->next) { -int err =e100_rx_indicate (nic, rx, work_done, work_to_do); -if (-EAGAIN == err) { -/* hit quota so have more work to do, restart once -* cleanup is complete */ - restart_required =0 ; + err =e100_rx_indicate (nic, rx, work_done, work_to_do); +/* Hit quota or no more to clean */ +if (-EAGAIN == err || -ENODATA == err)break ; - }else if (-ENODATA == err) -break ;/* No more to clean */ } -/* save our starting point as the place we'll restart the receiver */ -if (restart_required) - rx_to_start = nic->rx_to_clean; +/* +* On EAGAIN, hit quota so have more work to do, restart once +* cleanup is complete. +* Else, are we already rnr? then pay attention!!! this ensures that +* the state machine progression never allows a start with a +* partially cleaned list, avoiding a race between hardware +* and rx_to_clean when in NAPI mode +*/ +if (-EAGAIN != err && ru_stopped == nic->ru_running) + restart_required =1 ; + + marked_rx = nic->rx_to_use->prev->prev; +if (!(marked_rx->flags & rx_el)) { + marked_rx = marked_rx->prev; +BUG_ON (!marked_rx->flags & rx_el); + }/* Alloc new skbs to refill list */ for (rx = nic->rx_to_use; !rx->skb; rx = nic->rx_to_use = rx->next) {
@@ -1898,10 +1986,12 @@ static void e100_rx_clean(struct nic *nibreak ;/* Better luck next time (see watchdog) */ } +e100_find_mark_el (nic, marked_rx, !restart_required); +if (restart_required) {// ack the rnr? writeb (stat_ack_rnr, &nic->csr->scb.stat_ack); -e100_start_receiver (nic, rx_to_start); +e100_start_receiver (nic);if (work_done) (*work_done)++; }
@@ -1912,8 +2002,6 @@ static void e100_rx_clean_list(struct nistruct rx *rx;unsigned int i, count = nic->params.rfds.count; - nic->ru_running =RU_UNINITIALIZED ; -if (nic->rxs) {for (rx = nic->rxs, i =0 ; i < count; rx++, i++) {if (rx->skb) {
@@ -1935,7 +2023,6 @@ static int e100_rx_alloc_list(struct nicunsigned int i, count = nic->params.rfds.count; nic->rx_to_use = nic->rx_to_clean =NULL ; - nic->ru_running =RU_UNINITIALIZED ;if (!(nic->rxs =kcalloc (count,sizeof (struct rx ),GFP_ATOMIC )))return -ENOMEM ;
@@ -1950,7 +2037,9 @@ static int e100_rx_alloc_list(struct nic } nic->rx_to_use = nic->rx_to_clean = nic->rxs; - nic->ru_running =RU_SUSPENDED ; + nic->ru_running = ru_stopped; + +e100_find_mark_el (nic,NULL ,0 );return 0 ; }
@@ -1971,8 +2060,8 @@ static irqreturn_t e100_intr(int irq, voiowrite8 (stat_ack, &nic->csr->scb.stat_ack);/* We hit Receive No Resource (RNR); restart RU after cleaning */ -if (stat_ack & stat_ack_rnr) - nic->ru_running =RU_SUSPENDED ; +if (stat_ack & stat_ack_rnr) + nic->ru_running = ru_stopped;if (likely (netif_rx_schedule_prep (netdev))) {e100_disable_irq (nic);
@@ -2065,7 +2154,7 @@ static int e100_up(struct nic *nic)if ((err =e100_hw_init (nic))) goto err_clean_cbs;e100_set_multicast_list (nic->netdev); -e100_start_receiver (nic,NULL ); +e100_start_receiver (nic);mod_timer (&nic->watchdog, jiffies);if ((err =request_irq (nic->pdev->irq, e100_intr,IRQF_SHARED , nic->netdev->name, nic->netdev)))
@@ -2146,7 +2235,7 @@ static int e100_loopback_test(struct nicmdio_write (nic->netdev, nic->mii.phy_id,MII_BMCR ,BMCR_LOOPBACK ); -e100_start_receiver (nic,NULL ); +e100_start_receiver (nic);if (!(skb =netdev_alloc_skb (nic->netdev,ETH_DATA_LEN ))) { err = -ENOMEM ;
Quoted 37 lines · David Acker
On the systems that have cache incoherent DMA, including ARM, there is a race condition between software allocating a new receive buffer and hardware writing into a buffer. The two race on touching the last Receive Frame Descriptor (RFD). It has its el-bit set and its next link equal to 0. When hardware encounters this buffer it attempts to write data to it and then update Status Word bits and Actual Count in the RFD. At the same time software may try to clear the el-bit and set the link address to a new buffer.
Since the entire RFD is once cache-line, the two write operations can collide. This can lead to the receive unit stalling or interpreting random memory as its receive area.
The fix is to set the el-bit on and the size to 0 on the next to last buffer in the chain. When the hardware encounters this buffer it stops and does not write to it at all. The hardware issues an RNR interrupt with the receive unit in the No Resources state. Software can write to the tail of the list because it knows hardware will stop on the previous descriptor that was marked as the end of list.
Once it has a new next to last buffer prepared, it can clear the el-bit and set the size on the previous one. The race on this buffer is safe since the link already points to a valid next buffer and the software can handle the race setting the size (assuming aligned 16 bit writes are atomic with respect to the DMA read). If the hardware sees the el-bit cleared without the size set, it will move on to the next buffer and skip this one. If it sees the size set but the el-bit still set, it will complete that buffer and then RNR interrupt and wait.
Flags are kept in the software descriptor to note if the el bit is set and if the size was 0. When software clears the RFD's el bit and set its size, it also clears the el flag but leaves the size was 0 bit set. This way software can identify them when the race may have occurred when cleaning the ring. On these descriptors, it looks ahead and if the next one is complete then hardware must have skipped the current one. Logic is added to prevent two packets in a row being marked while the receiver is running to avoid running in lockstep with the hardware and thereby limiting the required lookahead.
Quoted 3 lines
This is a patch for 2.6.23-rc4.
Signed-off-by David Acker <[email protected]>
thanks David,
I'm going to try to give this some decent testing on x86 in the next two weeks, I'll let everyone know how this is going and take a look at the patch a bit later in -depth.
Auke
Quoted 323 lines
---
drivers/net/e100.c renamed from drivers/net/e100.c.orig +135
-46@@ -106,6 +106,13 @@* the RFD, the RFD must be dma_sync'ed to maintain a consistent * view from software and hardware. * +* In order to keep updates to the RFD link field from colliding with +* hardware writes to mark packets complete, we use the feature that +* hardware will not write to a size 0 descriptor and mark the previous +* packet as end-of-list (EL). After updating the link, we remove EL +* and only then restore the size such that hardware may use the +* previous-to-end RFD. +* * Under typical operation, the receive unit (RU) is start once, * and the controller happily fills RFDs as frames arrive. If * replacement RFDs cannot be allocated, or the RU goes non-active, @@ -281,14 +288,14 @@ struct csr { };enum scb_status { + rus_no_res =0x08 , rus_ready =0x10 , rus_mask =0x3C , };enum ru_state { -RU_SUSPENDED =0 , -RU_RUNNING =1 , -RU_UNINITIALIZED =-1 , + ru_stopped =0 , + ru_running =1 , };enum scb_stat_ack {@@ -401,10 +408,16 @@ struct rfd {u16 size; }; +enum rx_flags { + rx_el =0x01 , + rx_s0 =0x02 , +}; +struct rx {struct rx *next, *prev;struct sk_buff *skb;dma_addr_t dma_addr; +u8 flags; };#if defined(__BIG_ENDIAN_BITFIELD)@@ -952,7 +965,7 @@ static void e100_get_defaults(struct nic ((nic->mac >= mac_82558_D101_A4) ? cb_cid : cb_i));/* Template for a freshly allocated RFD */ - nic->blank_rfd.command =cpu_to_le16 (cb_el); + nic->blank_rfd.command =0 ; nic->blank_rfd.rbd =0xFFFFFFFF ; nic->blank_rfd.size =cpu_to_le16 (VLAN_ETH_FRAME_LEN );@@ -1753,18 +1766,48 @@ static int e100_alloc_cbs(struct nic *nireturn 0 ; } -static inline void e100_start_receiver (struct nic *nic,struct rx *rx) +static void e100_find_mark_el (struct nic *nic,struct rx *marked_rx,int is_running) { -if (!nic->rxs)return ; -if (RU_SUSPENDED != nic->ru_running)return ; +struct rx *rx = nic->rx_to_use->prev->prev; +struct rfd *rfd; + +if (marked_rx == rx) +return ; + + rfd = (struct rfd *) rx->skb->data; + rfd->command |=cpu_to_le16 (cb_el); + rfd->size =0 ; +pci_dma_sync_single_for_device (nic->pdev, rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); + rx->flags |= (rx_el | rx_s0); + +if (!marked_rx) +return ; + + rfd = (struct rfd *) marked_rx->skb->data; + rfd->command &= ~cpu_to_le16 (cb_el); +pci_dma_sync_single_for_device (nic->pdev, marked_rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); + + rfd->size =cpu_to_le16 (VLAN_ETH_FRAME_LEN ); +pci_dma_sync_single_for_device (nic->pdev, marked_rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); -/* handle init time starts */ -if (!rx) rx = nic->rxs; +if (is_running) + marked_rx->flags &= ~rx_el; +else + marked_rx->flags &= ~(rx_el | rx_s0); +} + +static inline void e100_start_receiver (struct nic *nic) +{ +if (!nic->rxs)return ; +if (ru_stopped != nic->ru_running)return ;/* (Re)start RU if suspended or idle and RFA is non-NULL */ -if (rx->skb) { -e100_exec_cmd (nic, ruc_start, rx->dma_addr); - nic->ru_running =RU_RUNNING ; +if (nic->rx_to_clean->skb) { +e100_exec_cmd (nic, ruc_start, nic->rx_to_clean->dma_addr); + nic->ru_running = ru_running; } }@@ -1793,8 +1836,6 @@ static int e100_rx_alloc_skb(struct nicstruct rfd *prev_rfd = (struct rfd *)rx->prev->skb->data;put_unaligned (cpu_to_le32 (rx->dma_addr), (u32 *)&prev_rfd->link); -wmb (); - prev_rfd->command &= ~cpu_to_le16 (cb_el);pci_dma_sync_single_for_device (nic->pdev, rx->prev->dma_addr,sizeof (struct rfd ),PCI_DMA_TODEVICE ); }@@ -1808,6 +1849,7 @@ static int e100_rx_indicate(struct nic *struct sk_buff *skb = rx->skb;struct rfd *rfd = (struct rfd *)skb->data;u16 rfd_status, actual_size; +u8 status;if (unlikely (work_done && *work_done >= work_to_do))return -EAGAIN ;@@ -1819,9 +1861,47 @@ static int e100_rx_indicate(struct nic *DPRINTK (RX_STATUS ,DEBUG ,"status=0x%04X\n" , rfd_status); -/* If data isn't ready, nothing to indicate */ -if (unlikely (!(rfd_status & cb_complete))) +/* +* If data isn't ready, nothing to indicate +* If both the el and s0 rx flags are set, we have hit the marked +* buffer but we don't know if hardware has seen it so we check +* the status. +* If only the s0 flag is set, we check the next buffer. +* If it is complete, we know that hardware saw the rfd el bit +* get cleared but did not see the rfd size get set so it +* skipped this buffer. We just return 0 and look at the +* next buffer. +* If only the s0 flag is set but the next buffer is +* not complete, we cleared the el flag as hardware +* hit this buffer. +*/ +if (unlikely (!(rfd_status & cb_complete))) { +u8 maskedFlags = rx->flags & (rx_el | rx_s0); +if (maskedFlags == (rx_el | rx_s0)) { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + }else if (maskedFlags == rx_s0) { +struct rx *next_rx = rx->next; +struct rfd *next_rfd = (struct rfd *)next_rx->skb->data; +pci_dma_sync_single_for_cpu (nic->pdev, + next_rx->dma_addr,sizeof (struct rfd ), +PCI_DMA_FROMDEVICE ); +if (next_rfd->status &cpu_to_le16 (cb_complete)) { +pci_unmap_single (nic->pdev, rx->dma_addr, +RFD_BUF_LEN ,PCI_DMA_FROMDEVICE ); +dev_kfree_skb_any (skb); + rx->skb =NULL ; + rx->flags &= ~rx_s0; +return 0 ; + }else { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + } + }return -ENODATA ; + }/* Get actual data size */ actual_size =le16_to_cpu (rfd->actual_size) &0x3FFF ;@@ -1832,9 +1912,15 @@ static int e100_rx_indicate(struct nic *pci_unmap_single (nic->pdev, rx->dma_addr,RFD_BUF_LEN ,PCI_DMA_FROMDEVICE ); -/* this allows for a fast restart without re-enabling interrupts */ -if (le16_to_cpu (rfd->command) & cb_el) - nic->ru_running =RU_SUSPENDED ; +/* +* This happens when hardward sees the rfd el flag set +* but then sees the rfd size set as well +*/ +if (le16_to_cpu (rfd->command) & cb_el) { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + }/* Pull off the RFD and put the actual data (minus eth hdr) */ skb_reserve (skb,sizeof (struct rfd ));@@ -1865,32 +1951,34 @@ static int e100_rx_indicate(struct nic *static void e100_rx_clean (struct nic *nic,unsigned int *work_done,unsigned int work_to_do) { -struct rx *rx; +struct rx *rx, *marked_rx;int restart_required =0 ; -struct rx *rx_to_start =NULL ; - -/* are we already rnr? then pay attention!!! this ensures that -* the state machine progression never allows a start with a -* partially cleaned list, avoiding a race between hardware -* and rx_to_clean when in NAPI mode */ -if (RU_SUSPENDED == nic->ru_running) - restart_required =1 ; +int err =0 ;/* Indicate newly arrived packets */ for (rx = nic->rx_to_clean; rx->skb; rx = nic->rx_to_clean = rx->next) { -int err =e100_rx_indicate (nic, rx, work_done, work_to_do); -if (-EAGAIN == err) { -/* hit quota so have more work to do, restart once -* cleanup is complete */ - restart_required =0 ; + err =e100_rx_indicate (nic, rx, work_done, work_to_do); +/* Hit quota or no more to clean */ +if (-EAGAIN == err || -ENODATA == err)break ; - }else if (-ENODATA == err) -break ;/* No more to clean */ } -/* save our starting point as the place we'll restart the receiver */ -if (restart_required) - rx_to_start = nic->rx_to_clean; +/* +* On EAGAIN, hit quota so have more work to do, restart once +* cleanup is complete. +* Else, are we already rnr? then pay attention!!! this ensures that +* the state machine progression never allows a start with a +* partially cleaned list, avoiding a race between hardware +* and rx_to_clean when in NAPI mode +*/ +if (-EAGAIN != err && ru_stopped == nic->ru_running) + restart_required =1 ; + + marked_rx = nic->rx_to_use->prev->prev; +if (!(marked_rx->flags & rx_el)) { + marked_rx = marked_rx->prev; +BUG_ON (!marked_rx->flags & rx_el); + }/* Alloc new skbs to refill list */ for (rx = nic->rx_to_use; !rx->skb; rx = nic->rx_to_use = rx->next) {@@ -1898,10 +1986,12 @@ static void e100_rx_clean(struct nic *nibreak ;/* Better luck next time (see watchdog) */ } +e100_find_mark_el (nic, marked_rx, !restart_required); +if (restart_required) {// ack the rnr? writeb (stat_ack_rnr, &nic->csr->scb.stat_ack); -e100_start_receiver (nic, rx_to_start); +e100_start_receiver (nic);if (work_done) (*work_done)++; }@@ -1912,8 +2002,6 @@ static void e100_rx_clean_list(struct nistruct rx *rx;unsigned int i, count = nic->params.rfds.count; - nic->ru_running =RU_UNINITIALIZED ; -if (nic->rxs) {for (rx = nic->rxs, i =0 ; i < count; rx++, i++) {if (rx->skb) {@@ -1935,7 +2023,6 @@ static int e100_rx_alloc_list(struct nicunsigned int i, count = nic->params.rfds.count; nic->rx_to_use = nic->rx_to_clean =NULL ; - nic->ru_running =RU_UNINITIALIZED ;if (!(nic->rxs =kcalloc (count,sizeof (struct rx ),GFP_ATOMIC )))return -ENOMEM ;@@ -1950,7 +2037,9 @@ static int e100_rx_alloc_list(struct nic } nic->rx_to_use = nic->rx_to_clean = nic->rxs; - nic->ru_running =RU_SUSPENDED ; + nic->ru_running = ru_stopped; + +e100_find_mark_el (nic,NULL ,0 );return 0 ; }@@ -1971,8 +2060,8 @@ static irqreturn_t e100_intr(int irq, voiowrite8 (stat_ack, &nic->csr->scb.stat_ack);/* We hit Receive No Resource (RNR); restart RU after cleaning */ -if (stat_ack & stat_ack_rnr) - nic->ru_running =RU_SUSPENDED ; +if (stat_ack & stat_ack_rnr) + nic->ru_running = ru_stopped;if (likely (netif_rx_schedule_prep (netdev))) {e100_disable_irq (nic);@@ -2065,7 +2154,7 @@ static int e100_up(struct nic *nic)if ((err =e100_hw_init (nic))) goto err_clean_cbs;e100_set_multicast_list (nic->netdev); -e100_start_receiver (nic,NULL ); +e100_start_receiver (nic);mod_timer (&nic->watchdog, jiffies);if ((err =request_irq (nic->pdev->irq, e100_intr,IRQF_SHARED , nic->netdev->name, nic->netdev)))
drivers/net/e100.c static int e100_loopback_test(struct nic · line 2241
Quoted 8 lines
drivers/net/e100.c renamed from drivers/net/e100.c.orig +1
-1@@ -2146,7 +2235,7 @@ static int e100_loopback_test(struct nicmdio_write (nic->netdev, nic->mii.phy_id,MII_BMCR ,BMCR_LOOPBACK ); -e100_start_receiver (nic,NULL ); +e100_start_receiver (nic);if (!(skb =netdev_alloc_skb (nic->netdev,ETH_DATA_LEN ))) { err = -ENOMEM ;
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
Quoted 37 lines · David Acker
On the systems that have cache incoherent DMA, including ARM, there is a race condition between software allocating a new receive buffer and hardware writing into a buffer. The two race on touching the last Receive Frame Descriptor (RFD). It has its el-bit set and its next link equal to 0. When hardware encounters this buffer it attempts to write data to it and then update Status Word bits and Actual Count in the RFD. At the same time software may try to clear the el-bit and set the link address to a new buffer.
Since the entire RFD is once cache-line, the two write operations can collide. This can lead to the receive unit stalling or interpreting random memory as its receive area.
The fix is to set the el-bit on and the size to 0 on the next to last buffer in the chain. When the hardware encounters this buffer it stops and does not write to it at all. The hardware issues an RNR interrupt with the receive unit in the No Resources state. Software can write to the tail of the list because it knows hardware will stop on the previous descriptor that was marked as the end of list.
Once it has a new next to last buffer prepared, it can clear the el-bit and set the size on the previous one. The race on this buffer is safe since the link already points to a valid next buffer and the software can handle the race setting the size (assuming aligned 16 bit writes are atomic with respect to the DMA read). If the hardware sees the el-bit cleared without the size set, it will move on to the next buffer and skip this one. If it sees the size set but the el-bit still set, it will complete that buffer and then RNR interrupt and wait.
Flags are kept in the software descriptor to note if the el bit is set and if the size was 0. When software clears the RFD's el bit and set its size, it also clears the el flag but leaves the size was 0 bit set. This way software can identify them when the race may have occurred when cleaning the ring. On these descriptors, it looks ahead and if the next one is complete then hardware must have skipped the current one. Logic is added to prevent two packets in a row being marked while the receiver is running to avoid running in lockstep with the hardware and thereby limiting the required lookahead.
Quoted 3 lines
This is a patch for 2.6.23-rc4.
Signed-off-by David Acker <[email protected]>
first impressions are not good: pings are erratic and shoot up to 3 seconds. In an overnight stress test, the receive unit went offline and never came back up (TX still working).
it sounds like something in the logic is suspending the ru too much, but I haven't had time to look deeply into the code yet.
Auke
Quoted 331 lines
---
drivers/net/e100.c renamed from drivers/net/e100.c.orig +136
-47@@ -106,6 +106,13 @@* the RFD, the RFD must be dma_sync'ed to maintain a consistent * view from software and hardware. * +* In order to keep updates to the RFD link field from colliding with +* hardware writes to mark packets complete, we use the feature that +* hardware will not write to a size 0 descriptor and mark the previous +* packet as end-of-list (EL). After updating the link, we remove EL +* and only then restore the size such that hardware may use the +* previous-to-end RFD. +* * Under typical operation, the receive unit (RU) is start once, * and the controller happily fills RFDs as frames arrive. If * replacement RFDs cannot be allocated, or the RU goes non-active, @@ -281,14 +288,14 @@ struct csr { };enum scb_status { + rus_no_res =0x08 , rus_ready =0x10 , rus_mask =0x3C , };enum ru_state { -RU_SUSPENDED =0 , -RU_RUNNING =1 , -RU_UNINITIALIZED =-1 , + ru_stopped =0 , + ru_running =1 , };enum scb_stat_ack {@@ -401,10 +408,16 @@ struct rfd {u16 size; }; +enum rx_flags { + rx_el =0x01 , + rx_s0 =0x02 , +}; +struct rx {struct rx *next, *prev;struct sk_buff *skb;dma_addr_t dma_addr; +u8 flags; };#if defined(__BIG_ENDIAN_BITFIELD)@@ -952,7 +965,7 @@ static void e100_get_defaults(struct nic ((nic->mac >= mac_82558_D101_A4) ? cb_cid : cb_i));/* Template for a freshly allocated RFD */ - nic->blank_rfd.command =cpu_to_le16 (cb_el); + nic->blank_rfd.command =0 ; nic->blank_rfd.rbd =0xFFFFFFFF ; nic->blank_rfd.size =cpu_to_le16 (VLAN_ETH_FRAME_LEN );@@ -1753,18 +1766,48 @@ static int e100_alloc_cbs(struct nic *nireturn 0 ; } -static inline void e100_start_receiver (struct nic *nic,struct rx *rx) +static void e100_find_mark_el (struct nic *nic,struct rx *marked_rx,int is_running) { -if (!nic->rxs)return ; -if (RU_SUSPENDED != nic->ru_running)return ; +struct rx *rx = nic->rx_to_use->prev->prev; +struct rfd *rfd; + +if (marked_rx == rx) +return ; + + rfd = (struct rfd *) rx->skb->data; + rfd->command |=cpu_to_le16 (cb_el); + rfd->size =0 ; +pci_dma_sync_single_for_device (nic->pdev, rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); + rx->flags |= (rx_el | rx_s0); + +if (!marked_rx) +return ; + + rfd = (struct rfd *) marked_rx->skb->data; + rfd->command &= ~cpu_to_le16 (cb_el); +pci_dma_sync_single_for_device (nic->pdev, marked_rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); + + rfd->size =cpu_to_le16 (VLAN_ETH_FRAME_LEN ); +pci_dma_sync_single_for_device (nic->pdev, marked_rx->dma_addr, +sizeof (struct rfd ),PCI_DMA_BIDIRECTIONAL ); -/* handle init time starts */ -if (!rx) rx = nic->rxs; +if (is_running) + marked_rx->flags &= ~rx_el; +else + marked_rx->flags &= ~(rx_el | rx_s0); +} + +static inline void e100_start_receiver (struct nic *nic) +{ +if (!nic->rxs)return ; +if (ru_stopped != nic->ru_running)return ;/* (Re)start RU if suspended or idle and RFA is non-NULL */ -if (rx->skb) { -e100_exec_cmd (nic, ruc_start, rx->dma_addr); - nic->ru_running =RU_RUNNING ; +if (nic->rx_to_clean->skb) { +e100_exec_cmd (nic, ruc_start, nic->rx_to_clean->dma_addr); + nic->ru_running = ru_running; } }@@ -1793,8 +1836,6 @@ static int e100_rx_alloc_skb(struct nicstruct rfd *prev_rfd = (struct rfd *)rx->prev->skb->data;put_unaligned (cpu_to_le32 (rx->dma_addr), (u32 *)&prev_rfd->link); -wmb (); - prev_rfd->command &= ~cpu_to_le16 (cb_el);pci_dma_sync_single_for_device (nic->pdev, rx->prev->dma_addr,sizeof (struct rfd ),PCI_DMA_TODEVICE ); }@@ -1808,6 +1849,7 @@ static int e100_rx_indicate(struct nic *struct sk_buff *skb = rx->skb;struct rfd *rfd = (struct rfd *)skb->data;u16 rfd_status, actual_size; +u8 status;if (unlikely (work_done && *work_done >= work_to_do))return -EAGAIN ;@@ -1819,9 +1861,47 @@ static int e100_rx_indicate(struct nic *DPRINTK (RX_STATUS ,DEBUG ,"status=0x%04X\n" , rfd_status); -/* If data isn't ready, nothing to indicate */ -if (unlikely (!(rfd_status & cb_complete))) +/* +* If data isn't ready, nothing to indicate +* If both the el and s0 rx flags are set, we have hit the marked +* buffer but we don't know if hardware has seen it so we check +* the status. +* If only the s0 flag is set, we check the next buffer. +* If it is complete, we know that hardware saw the rfd el bit +* get cleared but did not see the rfd size get set so it +* skipped this buffer. We just return 0 and look at the +* next buffer. +* If only the s0 flag is set but the next buffer is +* not complete, we cleared the el flag as hardware +* hit this buffer. +*/ +if (unlikely (!(rfd_status & cb_complete))) { +u8 maskedFlags = rx->flags & (rx_el | rx_s0); +if (maskedFlags == (rx_el | rx_s0)) { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + }else if (maskedFlags == rx_s0) { +struct rx *next_rx = rx->next; +struct rfd *next_rfd = (struct rfd *)next_rx->skb->data; +pci_dma_sync_single_for_cpu (nic->pdev, + next_rx->dma_addr,sizeof (struct rfd ), +PCI_DMA_FROMDEVICE ); +if (next_rfd->status &cpu_to_le16 (cb_complete)) { +pci_unmap_single (nic->pdev, rx->dma_addr, +RFD_BUF_LEN ,PCI_DMA_FROMDEVICE ); +dev_kfree_skb_any (skb); + rx->skb =NULL ; + rx->flags &= ~rx_s0; +return 0 ; + }else { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + } + }return -ENODATA ; + }/* Get actual data size */ actual_size =le16_to_cpu (rfd->actual_size) &0x3FFF ;@@ -1832,9 +1912,15 @@ static int e100_rx_indicate(struct nic *pci_unmap_single (nic->pdev, rx->dma_addr,RFD_BUF_LEN ,PCI_DMA_FROMDEVICE ); -/* this allows for a fast restart without re-enabling interrupts */ -if (le16_to_cpu (rfd->command) & cb_el) - nic->ru_running =RU_SUSPENDED ; +/* +* This happens when hardward sees the rfd el flag set +* but then sees the rfd size set as well +*/ +if (le16_to_cpu (rfd->command) & cb_el) { + status =readb (&nic->csr->scb.status); +if (status & rus_no_res) + nic->ru_running = ru_stopped; + }/* Pull off the RFD and put the actual data (minus eth hdr) */ skb_reserve (skb,sizeof (struct rfd ));@@ -1865,32 +1951,34 @@ static int e100_rx_indicate(struct nic *static void e100_rx_clean (struct nic *nic,unsigned int *work_done,unsigned int work_to_do) { -struct rx *rx; +struct rx *rx, *marked_rx;int restart_required =0 ; -struct rx *rx_to_start =NULL ; - -/* are we already rnr? then pay attention!!! this ensures that -* the state machine progression never allows a start with a -* partially cleaned list, avoiding a race between hardware -* and rx_to_clean when in NAPI mode */ -if (RU_SUSPENDED == nic->ru_running) - restart_required =1 ; +int err =0 ;/* Indicate newly arrived packets */ for (rx = nic->rx_to_clean; rx->skb; rx = nic->rx_to_clean = rx->next) { -int err =e100_rx_indicate (nic, rx, work_done, work_to_do); -if (-EAGAIN == err) { -/* hit quota so have more work to do, restart once -* cleanup is complete */ - restart_required =0 ; + err =e100_rx_indicate (nic, rx, work_done, work_to_do); +/* Hit quota or no more to clean */ +if (-EAGAIN == err || -ENODATA == err)break ; - }else if (-ENODATA == err) -break ;/* No more to clean */ } -/* save our starting point as the place we'll restart the receiver */ -if (restart_required) - rx_to_start = nic->rx_to_clean; +/* +* On EAGAIN, hit quota so have more work to do, restart once +* cleanup is complete. +* Else, are we already rnr? then pay attention!!! this ensures that +* the state machine progression never allows a start with a +* partially cleaned list, avoiding a race between hardware +* and rx_to_clean when in NAPI mode +*/ +if (-EAGAIN != err && ru_stopped == nic->ru_running) + restart_required =1 ; + + marked_rx = nic->rx_to_use->prev->prev; +if (!(marked_rx->flags & rx_el)) { + marked_rx = marked_rx->prev; +BUG_ON (!marked_rx->flags & rx_el); + }/* Alloc new skbs to refill list */ for (rx = nic->rx_to_use; !rx->skb; rx = nic->rx_to_use = rx->next) {@@ -1898,10 +1986,12 @@ static void e100_rx_clean(struct nic *nibreak ;/* Better luck next time (see watchdog) */ } +e100_find_mark_el (nic, marked_rx, !restart_required); +if (restart_required) {// ack the rnr? writeb (stat_ack_rnr, &nic->csr->scb.stat_ack); -e100_start_receiver (nic, rx_to_start); +e100_start_receiver (nic);if (work_done) (*work_done)++; }@@ -1912,8 +2002,6 @@ static void e100_rx_clean_list(struct nistruct rx *rx;unsigned int i, count = nic->params.rfds.count; - nic->ru_running =RU_UNINITIALIZED ; -if (nic->rxs) {for (rx = nic->rxs, i =0 ; i < count; rx++, i++) {if (rx->skb) {@@ -1935,7 +2023,6 @@ static int e100_rx_alloc_list(struct nicunsigned int i, count = nic->params.rfds.count; nic->rx_to_use = nic->rx_to_clean =NULL ; - nic->ru_running =RU_UNINITIALIZED ;if (!(nic->rxs =kcalloc (count,sizeof (struct rx ),GFP_ATOMIC )))return -ENOMEM ;@@ -1950,7 +2037,9 @@ static int e100_rx_alloc_list(struct nic } nic->rx_to_use = nic->rx_to_clean = nic->rxs; - nic->ru_running =RU_SUSPENDED ; + nic->ru_running = ru_stopped; + +e100_find_mark_el (nic,NULL ,0 );return 0 ; }@@ -1971,8 +2060,8 @@ static irqreturn_t e100_intr(int irq, voiowrite8 (stat_ack, &nic->csr->scb.stat_ack);/* We hit Receive No Resource (RNR); restart RU after cleaning */ -if (stat_ack & stat_ack_rnr) - nic->ru_running =RU_SUSPENDED ; +if (stat_ack & stat_ack_rnr) + nic->ru_running = ru_stopped;if (likely (netif_rx_schedule_prep (netdev))) {e100_disable_irq (nic);@@ -2065,7 +2154,7 @@ static int e100_up(struct nic *nic)if ((err =e100_hw_init (nic))) goto err_clean_cbs;e100_set_multicast_list (nic->netdev); -e100_start_receiver (nic,NULL ); +e100_start_receiver (nic);mod_timer (&nic->watchdog, jiffies);if ((err =request_irq (nic->pdev->irq, e100_intr,IRQF_SHARED , nic->netdev->name, nic->netdev)))@@ -2146,7 +2235,7 @@ static int e100_loopback_test(struct nicmdio_write (nic->netdev, nic->mii.phy_id,MII_BMCR ,BMCR_LOOPBACK ); -e100_start_receiver (nic,NULL ); +e100_start_receiver (nic);if (!(skb =netdev_alloc_skb (nic->netdev,ETH_DATA_LEN ))) { err = -ENOMEM ;
Quoted 3 lines · Auke
first impressions are not good: pings are erratic and shoot up to 3 seconds. In an overnight stress test, the receive unit went offline and never came back up (TX still working).
it sounds like something in the logic is suspending the ru too much, but I haven't had time to look deeply into the code yet.
I don't have an e100 enabled x86 box handy but I will look into getting one setup.
I just applied this patch to my PXA255 based system http://www.compulab.co.il/x255/html/x255-cm-datasheet.htm . It is running 2.6.18.4 plus compulab patches plus some hostap patches plus the e100 patch. I get:
pings going from the embedded system to a desktop machine. 100 packets transmitted, 100 received, 0% packet loss, time 98996ms rtt min/avg/max/mdev = 0.239/0.728/1.512/0.571 ms
Pings going the from the desktop machine to the embedded system 100 packets transmitted, 100 received, 0% packet loss, time 99217ms rtt min/avg/max/mdev = 0.206/0.876/1.473/0.575 ms
iperf tcp from embedded to desktop gets:
[ 5] 0.0-100.0 sec 1007 MBytes 84.4 Mbits/sec
iperf udp from the embedded to the desktop gets (embedded told to send at 100mbps):
[ 5] Server Report: [ 5] 0.0-100.0 sec 947 MBytes 79.4 Mbits/sec 0.068 ms 16/675645 (0.0024%) [ 5] 0.0-100.0 sec 1 datagrams received out-of-order
iperf tcp from the desktop to the embedded gets:
[ 6] 0.0-100.0 sec 1.01 GBytes 86.4 Mbits/sec
iperf udp from the desktop to the embedded gets the following when the desktop sent at 100 mbps
[ 5] 0.0-100.0 sec 964 MBytes 80.8 Mbits/sec 0.359 ms 126467/813760 (16%) [ 5] 0.0-100.0 sec 1 datagrams received out-of-order
Boot messages for my e100 are:
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
PCI: enabling device 0000:00:09.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:00:09.0 to 64
e100: eth0: e100_probe: addr 0x10131000, irq 111, MAC addr 00:09:30:FF:F2:F6 cat /sys/bus/pci/drivers/e100/0000\:00\:09.0/{device,vendor,subsystem_device,subsystem_vendor} 0x12090x80860x00000x0000
It's on its own interrupt line:
cm-debian:~# cat /proc/interrupts |grep eth0 111: 402428 - eth0
lspci shows:
00:09.0 Ethernet controller: Intel Corporation 8255xER/82551IT Fast Ethernet Controller (rev 09)
Let me know if there is any other information I can provide you. I will look through the code to see what could be going on with your machine. I will also look into reproducing these results with a newer kernel. This may be tricky since compulab's patches are pretty stale and don't always apply easily.
-Ack
Quoted 13 lines · David Acker
Quoted 6 lines · Auke
first impressions are not good: pings are erratic and shoot up to 3 seconds. In an overnight stress test, the receive unit went offline and never came back up (TX still working).
it sounds like something in the logic is suspending the ru too much, but I haven't had time to look deeply into the code yet.
I don't have an e100 enabled x86 box handy but I will look into getting one setup.
I just applied this patch to my PXA255 based system http://www.compulab.co.il/x255/html/x255-cm-datasheet.htm . It is running 2.6.18.4 plus compulab patches plus some hostap patches plus the e100 patch. I get:
Quoted 7 lines
pings going from the embedded system to a desktop machine. 100 packets transmitted, 100 received, 0% packet loss, time 98996ms rtt min/avg/max/mdev = 0.239/0.728/1.512/0.571 ms
Pings going the from the desktop machine to the embedded system 100 packets transmitted, 100 received, 0% packet loss, time 99217ms rtt min/avg/max/mdev = 0.206/0.876/1.473/0.575 ms
ok, I just got a note from our lab saying that that particular system has the freak ping times even without your patch applied 8)
ignoring the ping issue, we still have the ru offline, but that could have possibly been caused by whatever is causing this ping issue... More testing is needed, and I'll try to find a system without the ping issue here first.
Auke
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
Quoted 14 lines · Auke
Quoted 13 lines · David Acker
Quoted 3 lines · Auke
first impressions are not good: pings are erratic and shoot up to 3 seconds. In an overnight stress test, the receive unit went offline and never came back up (TX still working).
it sounds like something in the logic is suspending the ru too much, but I haven't had time to look deeply into the code yet.
I don't have an e100 enabled x86 box handy but I will look into getting one setup.
I just applied this patch to my PXA255 based system http://www.compulab.co.il/x255/html/x255-cm-datasheet.htm . It is running 2.6.18.4 plus compulab patches plus some hostap patches plus the e100 patch. I get:
pings going from the embedded system to a desktop machine. 100 packets transmitted, 100 received, 0% packet loss, time 98996ms rtt min/avg/max/mdev = 0.239/0.728/1.512/0.571 ms
Quoted 7 lines
Quoted 3 lines
Pings going the from the desktop machine to the embedded system 100 packets transmitted, 100 received, 0% packet loss, time 99217ms rtt min/avg/max/mdev = 0.206/0.876/1.473/0.575 ms
ok, I just got a note from our lab saying that that particular system has the freak ping times even without your patch applied 8)
ignoring the ping issue, we still have the ru offline, but that could have possibly been caused by whatever is causing this ping issue... More testing is needed, and I'll try to find a system without the ping issue here first.
update: Emil reports that the unit with the RU hang did not have bad ping times to begin with, pointing to a problem with the patch for sure now...
Auke
Quoted 1 line · David Acker
Let me know if there is any other information I can provide you. I will look through the code to see what could be going on with your machine. I will also look into reproducing these results with a newer kernel. This may be tricky since compulab's patches are pretty stale and don't always apply easily.
pktgen outputs for the various cases modified/unmodified[/others?] would be nice, if you have a spot of time.
Jeff
Quoted 7 lines · Jeff Garzik
Quoted 1 line · David Acker
Let me know if there is any other information I can provide you. I will look through the code to see what could be going on with your machine. I will also look into reproducing these results with a newer kernel. This may be tricky since compulab's patches are pretty stale and don't always apply easily.
pktgen outputs for the various cases modified/unmodified[/others?] would be nice, if you have a spot of time.
Jeff
I am not familiar with pktgen but I seem to have it working for a simple test.
I edited the 1-1 example from ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/examples/ . The results with and without the patch are below. Let me know if you want any other tests run. I obtained a PCI to miniPCI adapter that will let me test my miniPCI based e100s on my main dev box. I will work on reproducing Intel's results tomorrow as time permits. I am also still trying to get time to work on a recent kernel merge. Not a lot changed in the 100 since 2.6.18.4 except a flip from readX/writeX to ioreadX/iowriteX.
-Ack
cm-debian:/tmp# ./pktgen.conf-1-1 Removing all devices Adding eth0 Setting max_before_softirq 10000 Configuring /proc/net/pktgen/eth0 Running... ctrl^C to stop Done
Here are the results on 2.6.18.4 with the patch I submitted on my embedded system.
cm-debian:/tmp# cat /proc/net/pktgen/eth0
Params: count 10000000 min_pkt_size: 60 max_pkt_size: 60
frags: 0 delay: 0 clone_skb: 1000000 ifname: eth0
flows: 0 flowlen: 0
dst_min: 192.168.1.40 dst_max:
src_min: src_max:
src_mac: 00:09:30:FF:F2:F6 dst_mac: 00:19:B9:0B:45:8E
udp_src_min: 9 udp_src_max: 9 udp_dst_min: 9 udp_dst_max: 9
src_mac_count: 0 dst_mac_count: 0
Flags:
Current:
pkts-sofar: 10000000 errors: 0
started: 14852031282115us stopped: 14852181463422us idle: 918us
seq_num: 10000011 cur_dst_mac_offset: 0 cur_src_mac_offset: 0
cur_saddr: 0x2901a8c0 cur_daddr: 0x2801a8c0
cur_udp_dst: 9 cur_udp_src: 9
flows: 0
Result: OK: 150181307(c150180389+d918) usec, 10000000 (60byte,0frags)
66586pps 31Mb/sec (31961280bps) errors: 0and here are the results without the patch:
cm-debian:/tmp# cat /proc/net/pktgen/eth0
Params: count 10000000 min_pkt_size: 60 max_pkt_size: 60
frags: 0 delay: 0 clone_skb: 1000000 ifname: eth0
flows: 0 flowlen: 0
dst_min: 192.168.1.40 dst_max:
src_min: src_max:
src_mac: 00:09:30:FF:F2:F6 dst_mac: 00:19:B9:0B:45:8E
udp_src_min: 9 udp_src_max: 9 udp_dst_min: 9 udp_dst_max: 9
src_mac_count: 0 dst_mac_count: 0
Flags:
Current:
pkts-sofar: 10000000 errors: 0
started: 14864204332576us stopped: 14864355451225us idle: 1431us
seq_num: 10000011 cur_dst_mac_offset: 0 cur_src_mac_offset: 0
cur_saddr: 0x2901a8c0 cur_daddr: 0x2801a8c0
cur_udp_dst: 9 cur_udp_src: 9
flows: 0
Result: OK: 151118649(c151117218+d1431) usec, 10000000 (60byte,0frags)
66173pps 31Mb/sec (31763040bps) errors: 0Quoted 11 lines · David Acker
Quoted 7 lines · Jeff Garzik
Quoted 1 line · David Acker
Let me know if there is any other information I can provide you. I will look through the code to see what could be going on with your machine. I will also look into reproducing these results with a newer kernel. This may be tricky since compulab's patches are pretty stale and don't always apply easily.
pktgen outputs for the various cases modified/unmodified[/others?] would be nice, if you have a spot of time.
Jeff
I am not familiar with pktgen but I seem to have it working for a simple test.
I edited the 1-1 example from ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/examples/ . The results with and without the patch are below.
It looks like you ran pktgen on the embedded system, which exercised only the transmit path. Auke indicated that the lockup was in the RU. Have you run pktgen on a test system to fire packets at the embedded system at max rate? Also test what happens when you fire packets in both directions simultaneously.
Signature · 4 lines
James Chapman Katalix Systems Ltd http://www.katalix.com Catalysts for your Embedded Linux software development
Quoted 11 lines · James Chapman
Quoted 7 lines · David Acker
Quoted 3 lines · Jeff Garzik
pktgen outputs for the various cases modified/unmodified[/others?] would be nice, if you have a spot of time.
Jeff
I am not familiar with pktgen but I seem to have it working for a simple test.
I edited the 1-1 example from ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/examples/ . The results with and without the patch are below.It looks like you ran pktgen on the embedded system, which exercised only the transmit path. Auke indicated that the lockup was in the RU. Have you run pktgen on a test system to fire packets at the embedded system at max rate? Also test what happens when you fire packets in both directions simultaneously.
It appears that running pktgen between my pc and the embedded device at the same time eventually hangs the RU. I will be looking into this failure in detail and report back when I know more. Thanks for bearing with me on this! -Ack