netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Frank Reppin <frank@undermydesk.org>, <netdev@vger.kernel.org>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	jesse.brandeburg@intel.com, e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH net] e1000e: Change wthresh to 1 to avoid possible Tx stalls.
Date: Tue, 9 Oct 2012 10:36:29 -0700	[thread overview]
Message-ID: <20121009103629.0000569a@unknown> (raw)
In-Reply-To: <1349762863.21172.3848.camel@edumazet-glaptop>

> > > Jesse did not share any performance numbers with me, I am sure he can
> > > give some background tomorrow when he is back online.
> > > 
> > > I am working on an alternative patch now and should have something to
> > > share tomorrow.
> > Please allow me to ask if there's any progess here?
> > 
> > I've tried 3.5.4 a couple of days ago on a SuperMicro X8SIE-LN4 (82574L)
> > and could still observe severe latency (up to 3000ms) spikes.
> > 
> > Applying Hiroakis suggested patch did fix this for me as well.
> > [please note as well that I didn't had this issue in any 3.4.x kernel
> > before - so +1 for fixing the regression]

I'm not sure what went wrong internally here that this hasn't been
fixed, and I'm personally embarrassed.  I am working on it until I have
a patch/solution.

currently am trying to reproduce the issue, am in some weird how to
use BQL limbo, the lack of documentation on user usage of BQL is slowing
me down.

Hints or clues (I'm trying to follow the repro steps mentioned in
some related threads) are appreciated.

  reply	other threads:[~2012-10-09 17:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06  8:43 [PATCH net] e1000e: Change wthresh to 1 to avoid possible Tx stalls 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 [this message]
2012-10-09 21:02             ` Eric Dumazet
2012-10-09 22:48             ` Andre Tomt
2012-10-10  1:25               ` Frank Reppin
  -- strict thread matches above, loose matches on Subject: below --
2012-10-11  1:34 [PATCH NET] " Jesse Brandeburg
2012-10-11  3:00 ` David Miller

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=20121009103629.0000569a@unknown \
    --to=jesse.brandeburg@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=eric.dumazet@gmail.com \
    --cc=frank@undermydesk.org \
    --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).