From: Frank Reppin <frank@undermydesk.org>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: netdev@vger.kernel.org,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH net] e1000e: Change wthresh to 1 to avoid possible Tx stalls.
Date: Wed, 10 Oct 2012 03:25:54 +0200 [thread overview]
Message-ID: <5074CEA2.6010504@undermydesk.org> (raw)
In-Reply-To: <5074A9CA.50308@tomt.net>
On 10.10.2012 00:48, Andre Tomt wrote:
> On 09. okt. 2012 19:36, Jesse Brandeburg wrote:
[...]
>> Hints or clues (I'm trying to follow the repro steps mentioned in
>> some related threads) are appreciated.
In our scenario - the SuperMicro X8SIE-LN4 acts
as a router.
eth0 -> uplink
eth1 -> core servers network 192.168.a.b/24
eth2 -> developer employees network 192.168.c.d/24
eth1 and eth2 are hooked into (two different) HP2510-24G
switches (they both show no errors at all).
The switch connected to eth2 connects a bunch of
developers doing day-2-day stuff (commits/checkouts/documentation/
listening to stream music/surfing/email) and the such.
Continously running a ping from ie. 192.168.c.d/24 to
192.168.a.b/24 visualizes those spikes (mostly triplets, where
the first echo reply is quite high and the two following replies
are each around 50 percent faster - but mostly still >500ms) - whenever
these spikes happen, it feels like the whole net 'stalls'.
Just like Denys Fedoryshchenko stated in
http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg05517.html
HTH,
Frank Reppin
--
43rd Law of Computing:
Anything that can go wr
fortune: Segmentation violation -- Core dumped
next prev parent reply other threads:[~2012-10-10 1:32 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
2012-10-09 21:02 ` Eric Dumazet
2012-10-09 22:48 ` Andre Tomt
2012-10-10 1:25 ` Frank Reppin [this message]
-- 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=5074CEA2.6010504@undermydesk.org \
--to=frank@undermydesk.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.