netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
	Erik Mouw <erik@harddisk-recovery.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: Transmit timeout with E1000
Date: Wed, 11 Jan 2006 15:48:11 +0100	[thread overview]
Message-ID: <20060111144810.GA25967@bitwizard.nl> (raw)
In-Reply-To: <43C51223.6040309@cosmosbay.com>

On Wed, Jan 11, 2006 at 03:11:47PM +0100, Eric Dumazet wrote:
> Rogier Wolff a écrit :
> >On Wed, Jan 11, 2006 at 02:43:49PM +0100, Erik Mouw wrote:
> >>The system only recovers after the Netdev watchdog found out that the
> >>transmit timed out. However, the e1000 register dump starts about 4 to
> >>5 seconds earlier: a possible workaround would be to trigger the
> >>timeout code path as soon as the register dump starts.
> >
> >Found a typo. 
> >
> >	Roger. 
> >
> >
> >--- e1000_main.c.orig	2006-01-11 14:53:23.000000000 +0100
> >+++ e1000_main.c	2006-01-11 14:53:38.000000000 +0100
> >@@ -3449,7 +3449,7 @@
> > 	}
> > 
> > 	for (i = 0; i < E1000_MAX_INTR; i++)
> >-		if (unlikely(!adapter->clean_rx(adapter, adapter->rx_ring) &
> >+		if (unlikely(!adapter->clean_rx(adapter, adapter->rx_ring) &&
> > 		   !e1000_clean_tx_irq(adapter, adapter->tx_ring)))
> > 			break;
> > 
> >
> >
> 
> I believe it's not a typo.
> 
> The intention is to call both clean_rx() and e1000_clean_tx_irq(), and 
> break of the loop if both said : There was no job pending.

Although (one of) the prototypes state(s) that it returns a boolean,
it is valid C to return the number of items pending.

And if one reports "2 more pending" and the other reports "1 more
pending", the "&" between the two becomes 2 & 1 => 0 / FALSE, while 2
&& 1 => TRUE.

I consider this a low prio typo, not likely to be a bug "right now",
but it is inviting someone to make it into a bug later on.

	Roger. 

-- 
+-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 --
| Files foetsie, bestanden kwijt, alle data weg?!
| Blijf kalm en neem contact op met Harddisk-recovery.nl!


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

  reply	other threads:[~2006-01-11 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 15:12 Transmit timeout with E1000 Erik Mouw
     [not found] ` <Pine.WNT.4.63.0601100929570.1360@jbrandeb-desk.amr.corp.intel.com>
2006-01-11 12:59   ` Erik Mouw
2006-01-11 13:22     ` Erik Mouw
2006-01-11 13:43       ` Erik Mouw
2006-01-11 13:56         ` Rogier Wolff
2006-01-11 14:11           ` Eric Dumazet
2006-01-11 14:48             ` Rogier Wolff [this message]
2006-01-11 14:51               ` Rogier Wolff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060111144810.GA25967@bitwizard.nl \
    --to=r.e.wolff@harddisk-recovery.nl \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=dada1@cosmosbay.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=erik@harddisk-recovery.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).