From: David Woodhouse <dwmw2@infradead.org>
To: Pete Skelly <pete.skelly@astanetworks.com>
Cc: "'mtd@infradead.org'" <mtd@infradead.org>
Subject: Re: DOC2000 - 96MB on a 650Mhz PIII - cannot doc_read_ecc
Date: Tue, 06 Mar 2001 08:53:21 +0000 [thread overview]
Message-ID: <3970.983868801@redhat.com> (raw)
In-Reply-To: <15E6537E180CC545848148F30F6688D81945CF@navajo.astanetworks.com>
pete.skelly@astanetworks.com said:
> A number of people have indicated they have been having problems with
> larger DoC devices, and I suspect this may in fact be the problem.
> Either the page swap delay is longer on larger devices, or they are
> running on faster machines.
Hmmm. It doesn't seem to fix my 72MiB DiskOnChip, even when I move the
delay to between the data read and the ecc read.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-03-06 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 22:48 DOC2000 - 96MB on a 650Mhz PIII - cannot doc_read_ecc Pete Skelly
2001-03-06 8:53 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-02 8:38 Pete Skelly
2001-03-02 8:57 ` David Woodhouse
2001-03-02 11:06 ` Ollie Lho
2001-03-02 0:58 Pete Skelly
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=3970.983868801@redhat.com \
--to=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=pete.skelly@astanetworks.com \
/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