netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: bruce.w.allan@intel.com, netdev@vger.kernel.org,
	gospo@redhat.com, bphilips@novell.com
Subject: Re: [net-next-2.6 03/16] e1000e: do not wakeup Tx queue until ready
Date: Tue, 08 Feb 2011 12:21:15 -0800 (PST)	[thread overview]
Message-ID: <20110208.122115.183054158.davem@davemloft.net> (raw)
In-Reply-To: <1297168167-15755-4-git-send-email-jeffrey.t.kirsher@intel.com>

From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Tue,  8 Feb 2011 04:29:14 -0800

> From: Bruce Allan <bruce.w.allan@intel.com>
> 
> When restarting the adapter via calls to e1000e_down() followed by
> e1000e_up() (for example when restarting autonegotiation via ethtool),
> packets can be queued for transmit before link is actually up and
> netif_carrier_on is set.  This was causing the watchdog_task to do an
> extra unnecessary reset of the adapter.  Delaying the wakeup of the Tx
> queue until link is up prevents the reset.
> 
> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
> Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

You should not control the TX queue based upon link status information.
That's the job of netif_carrier_{on,off}().

The TX queue state should be set based solely upon that state of the
TX ring, whether it is full or not.

When the netif carrier is off, the packet scheduler is blocked from
sending packets to the driver.

If that isn't happening, that's a bug which you need to track down.
Maybe you're not doing netif_carrier_off() early enough.

  reply	other threads:[~2011-02-08 20:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 12:29 [net-next-2.6 00/16][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 01/16] e1000e: replace unbounded sprintf with snprintf Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 02/16] e1000e: use correct pointer when memcpy'ing a 2-dimensional array Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 03/16] e1000e: do not wakeup Tx queue until ready Jeff Kirsher
2011-02-08 20:21   ` David Miller [this message]
2011-02-08 20:52     ` Allan, Bruce W
2011-02-08 12:29 ` [net-next-2.6 04/16] e1000e: return appropriate errors for 'ethtool -r' Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 05/16] igb: Enable PF side of SR-IOV support for i350 devices Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 06/16] ixgbe: DCB, only reprogram HW if the FCoE priority is changed Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 07/16] ixgbe: DCB, remove round robin mode on 82598 devices Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 08/16] ixgbe: DCB, abstract out dcb_config from DCB hardware configuration Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 09/16] ixgbe: DCB, implement 802.1Qaz routines Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 10/16] ixgbe: DCB, do not reset on CEE pg changes Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 11/16] ixgbe: DCB, remove RESET bit it is no longer needed Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 12/16] ixgbe: dcb, use hardware independent routines Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 13/16] ixgbe: fix namespace issue with ixgbe_dcb_txq_to_tc Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 14/16] ixgbe: cleanup namespace complaint by removing little used function Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 15/16] ixgbe: cleanup ixgbe_init_mbx_params_pf namespace issue Jeff Kirsher
2011-02-08 12:29 ` [net-next-2.6 16/16] ixgbe: Adding 100MB FULL support in ethtool Jeff Kirsher
2011-02-11 15:55 ` [net-next-2.6 00/16][pull request] Intel Wired LAN Driver Updates Jeff Kirsher

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=20110208.122115.183054158.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bphilips@novell.com \
    --cc=bruce.w.allan@intel.com \
    --cc=gospo@redhat.com \
    --cc=jeffrey.t.kirsher@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).