netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jesse.brandeburg@intel.com
Cc: netdev@vger.kernel.org, shimoda.hiroaki@gmail.com,
	eric.dumazet@gmail.com, therbert@google.com
Subject: Re: [PATCH NET] e1000e: Change wthresh to 1 to avoid possible Tx stalls
Date: Wed, 10 Oct 2012 23:00:00 -0400 (EDT)	[thread overview]
Message-ID: <20121010.230000.1520707219906312743.davem@davemloft.net> (raw)
In-Reply-To: <20121011013420.30383.27700.stgit@jbrandeb-snb.jf.intel.com>

From: Jesse Brandeburg <jesse.brandeburg@intel.com>
Date: Wed, 10 Oct 2012 18:34:20 -0700

> From: Hiroaki SHIMODA <shimoda.hiroaki@gmail.com>
> 
> This patch originated from Hiroaki SHIMODA but has been modified
> by Intel with some minor cleanups and additional commit log text.
> 
> Denys Fedoryshchenko and others reported Tx stalls on e1000e with
> BQL enabled.  Issue was root caused to hardware delays. They were
> introduced because some of the e1000e hardware with transmit
> writeback bursting enabled, waits until the driver does an
> explict flush OR there are WTHRESH descriptors to write back.
> 
> Sometimes the delays in question were on the order of seconds,
> causing visible lag for ssh sessions and unacceptable tx
> completion latency, especially for BQL enabled kernels.
> 
> To avoid possible Tx stalls, change WTHRESH back to 1.
> 
> The current plan is to investigate a method for re-enabling
> WTHRESH while not harming BQL, but those patches will be later
> for net-next if they work.
> 
> please enqueue for stable since v3.3 as this bug was introduced in
> commit 3f0cfa3bc11e7f00c9994e0f469cbc0e7da7b00c
> Author: Tom Herbert <therbert@google.com>
> Date:   Mon Nov 28 16:33:16 2011 +0000
> 
>     e1000e: Support for byte queue limits
> 
>     Changes to e1000e to use byte queue limits.
> 
> Reported-by: Denys Fedoryshchenko <denys@visp.net.lb>
> Tested-by: Denys Fedoryshchenko <denys@visp.net.lb>
> Signed-off-by: Hiroaki SHIMODA <shimoda.hiroaki@gmail.com>
> CC: eric.dumazet@gmail.com
> CC: therbert@google.com
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>

Applied and queued up for -stable, thanks.

  reply	other threads:[~2012-10-11  3:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11  1:34 [PATCH NET] e1000e: Change wthresh to 1 to avoid possible Tx stalls Jesse Brandeburg
2012-10-11  3:00 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-06  8:43 [PATCH net] " Hiroaki SHIMODA
2012-06-06  8:46 ` Jeff Kirsher
2012-06-06  8:50 ` Eric Dumazet
2012-06-07  0:59 ` Jeff Kirsher
2012-06-07  1:34   ` David Miller
2012-06-07  4:24   ` Eric Dumazet
2012-06-07  4:52     ` Jeff Kirsher
2012-06-07  5:03       ` Eric Dumazet
2012-10-09  0:25       ` Frank Reppin
2012-10-09  6:07         ` Eric Dumazet
2012-10-09 17:36           ` Jesse Brandeburg
2012-10-09 21:02             ` Eric Dumazet
2012-10-09 22:48             ` Andre Tomt
2012-10-10  1:25               ` Frank Reppin

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=20121010.230000.1520707219906312743.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=shimoda.hiroaki@gmail.com \
    --cc=therbert@google.com \
    /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).