From: Jeff Garzik <jeff@garzik.org>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
jesse.brandeburg@intel.com
Subject: Re: [PATCH 1/4] e1000: disable TSO workaround on 82544
Date: Fri, 27 Jun 2008 01:13:27 -0400 [thread overview]
Message-ID: <486476F7.9010506@garzik.org> (raw)
In-Reply-To: <20080619211836.GC22981@gospo.rdu.redhat.com>
Andy Gospodarek wrote:
> It appears that the 82544 does not need the TSO workaround needed on
> other chips. This seems to resolve excessive messages that appear to be
> Tx Unit Hangs when a system is under heavy stress.
Do these excessive messages occur for all systems with the TSO
workaround? i.e. does this patch merely remove one chip from the list
of chips that receive excessive messages?
next prev parent reply other threads:[~2008-06-27 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 21:18 [PATCH 1/4] e1000: disable TSO workaround on 82544 Andy Gospodarek
2008-06-25 8:50 ` Jeff Kirsher
2008-06-27 5:13 ` Jeff Garzik [this message]
2008-06-27 14:25 ` Andy Gospodarek
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=486476F7.9010506@garzik.org \
--to=jeff@garzik.org \
--cc=andy@greyhouse.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 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).