netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Stephen Hemminger <shemminger-3NddpPZAyC0@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
	Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>,
	Stefano Brivio <st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
Subject: Re: netdev tx timeouts
Date: Wed, 13 Sep 2006 21:04:02 -0500	[thread overview]
Message-ID: <4508B892.4040309@lwfinger.net> (raw)
In-Reply-To: <20060914102337.137d4591-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

Stephen Hemminger wrote:
> On Wed, 13 Sep 2006 15:49:23 +0200
> Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org> wrote:
>> Simple. Reading the code of synchronize_net() and
>> netif_stop_queue() and thinking about why it breaks, instead
>> of committing bugfixes that only substitute one bug by another. ;)
>> I'll take a look, too.
> 
> Why are you doing the synchronize_net()? it is meant for RCU.

We know and it no longer is in the code. We have known for a couple of days that 
it was the synchronize_net() step that led to the netdev timeouts, but we were 
afraid that a bare netif_stop_queue would not be SMP safe. The current structure has

mutex_lock
netif_tx_disable(dev)   (equivalent to  netif_tx_lock_bh(dev);
				        netif_stop_queue(dev);
			                netif_tx_unlock_bh(dev);
spin_lock_irqsafe

I see you listed as a maintainer in several network-related parts of the system, 
so AFAIK, you are a network guru. Do you think this will work? I have tested 
code with just a netif_stop_queue (without the lock_bh/unlock_bh parts) on a UP 
system and have gotten no errors, but I do not have access to SMP hardware.

Thanks,

Larry

  parent reply	other threads:[~2006-09-14  2:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13  2:25 netdev tx timeouts Larry Finger
     [not found] ` <45076C00.2000100-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-13 12:30   ` Michael Buesch
     [not found]     ` <200609131430.53820.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-09-13 13:25       ` Larry Finger
2006-09-13 13:49         ` Michael Buesch
2006-09-13 14:12           ` Michael Buesch
2006-09-14  1:23           ` Stephen Hemminger
     [not found]             ` <20060914102337.137d4591-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-14  2:04               ` Larry Finger [this message]
2006-09-14  2:21                 ` Stephen Hemminger
2006-09-14  2:35                   ` Larry Finger

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=4508B892.4040309@lwfinger.net \
    --to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
    --cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shemminger-3NddpPZAyC0@public.gmane.org \
    --cc=st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.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).