From: Peter Tyser <ptyser@xes-inc.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] sky2: RX lockup fix
Date: Thu, 06 Dec 2007 10:14:57 -0600 [thread overview]
Message-ID: <1196957697.24978.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20071205225249.0f46672c@shemminger-laptop>
> I have ways to generate errors, so I'll check
Thanks Stephen. We didn't spend a lot of time characterizing the issue,
but our test setup had two blades, each with an 88E8062. Our test
software pumped UDP and TCP traffic of varying packet sizes between the
blades in both directions (including jumbo frames - we increased the
MTU of the interfaces to 9000). The issue could generally be brought
out in about 15 minutes and almost always within an hour.
If you'd like any additional details on the test setup or would like me
to try something on my end, let me know.
next prev parent reply other threads:[~2007-12-06 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 18:51 [PATCH] sky2: RX lockup fix Peter Tyser
2007-12-05 21:40 ` Stephen Hemminger
2007-12-06 0:18 ` Peter Tyser
2007-12-06 3:52 ` Stephen Hemminger
2007-12-06 16:14 ` Peter Tyser [this message]
2007-12-07 23:22 ` Stephen Hemminger
2007-12-14 20:26 ` Jeff Garzik
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=1196957697.24978.24.camel@localhost.localdomain \
--to=ptyser@xes-inc.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).