From: Pavel Machek <pavel@suse.cz>
To: "Stephen Gutknecht (linux-kernel)" <linux-kernel@i405.com>,
"'David Lang'" <david.lang@digitalinsight.com>,
David Riley <oscar@the-rileys.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Better testing of hardware (was: Defective Read Hat)
Date: Wed, 22 Nov 2000 00:22:05 +0100 [thread overview]
Message-ID: <20001122002205.B219@bug.ucw.cz> (raw)
In-Reply-To: <0066CB04D783714B88D83397CCBCA0CD49AF@spike2.i405.net>
In-Reply-To: <0066CB04D783714B88D83397CCBCA0CD49AF@spike2.i405.net>; from Stephen Gutknecht (linux-kernel) on Tue, Nov 21, 2000 at 01:39:17PM -0800
Hi!
> You will find that most Overlockers run their favorite game in a loop for 10
> or 20 minutes as the best test they have found. This often does
> Video+Ram+CPU+Sound board (PCI) at full tilt. What is needed is a
> _standardized test_ that really goes after everything (including network).
You don't need to test network that much: if your network card garbles
packets under high load, it is ok. TCP checksums should catch that.
(OTOH, on really broken serial cable (no flow control and machines
definitely miss characters sometimes), I can occassionaly see
corruption even with TCP. Ouch.)
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 21:39 Better testing of hardware (was: Defective Read Hat) Stephen Gutknecht (linux-kernel)
2000-11-21 21:46 ` Dan Hollis
2000-11-21 23:22 ` Pavel Machek [this message]
2000-11-22 1:27 ` Fort David
2000-11-22 7:13 ` Eric W. Biederman
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=20001122002205.B219@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@i405.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oscar@the-rileys.net \
/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