From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Poor floppy performance in kernel 2.4.10
Date: Thu, 18 Oct 2001 15:57:17 -0400 [thread overview]
Message-ID: <200110181957.f9IJvHh06884@deathstar.prodigy.com> (raw)
In-Reply-To: <200110181632.f9IGW9i29729@schroeder.cs.wisc.edu>
In article <200110181632.f9IGW9i29729@schroeder.cs.wisc.edu> nleroy@cs.wisc.edu wrote:
| Perhaps there should be a pair of "mtools" added: mopen and mclose, that do
| basically this. That way it could be a "standard" item, documented in man
| pages, etc., not some secret that only the l-k users know. Thoughts?
At the risk of seeming ungenerous, mtools was a hack, to compensate
for the inability of some operating systems to handle the DOS
filesystem. While it's useful, I don't thing blindingly fast performance
is a requirement.
That said, I have a few other thoughts. First, can't the kernel
detect when a new floppy is inserted? I can't remember if there is an
interupt generated when the floppy seats or not.
And second, can't you just avoid the whole issue by keeping the floppy
accessed at all time while you use it? Something like:
sleep 3600 </dev/fd0 &
or some such to lock the pages after they are read?
The change is a good one, it avoids having stale data in memory which
might cause worse things than slow performance. I think I have been
bitten by that in the past, but I don't remember any details, so it may
have been another problem.
--
bill davidsen <davidsen@tmr.com>
His first management concern is not solving the problem, but covering
his ass. If he lived in the middle ages he'd wear his codpiece backward.
next prev parent reply other threads:[~2001-10-18 19:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 7:36 Kamil Iskra
2001-10-17 20:45 ` Steve Kieu
2001-10-18 10:11 ` Kamil Iskra
2001-10-18 15:28 ` Andreas Dilger
2001-10-18 15:42 ` Kamil Iskra
2001-10-18 16:17 ` Ville Herva
2001-10-18 16:30 ` Nick LeRoy
2001-10-18 19:57 ` bill davidsen [this message]
2001-10-18 20:47 ` Nick LeRoy
2001-10-18 20:05 ` bill davidsen
2001-10-18 20:15 ` Alexander Viro
2001-10-18 16:18 ` Alexander Viro
2001-10-18 17:44 ` Andrea Arcangeli
2001-10-19 7:50 ` Giuliano Pochini
2001-10-19 13:46 ` Andrea Arcangeli
2001-10-19 15:57 ` Linus Torvalds
2001-10-20 4:20 ` Rob Landley
2001-10-19 16:58 Manfred Spraul
2001-10-21 11:36 Alain Knaff
2001-10-22 9:59 ` Andrea Arcangeli
2001-10-22 10:06 ` Alexander Viro
2001-10-22 14:07 ` Nick LeRoy
2001-10-22 18:28 ` bill davidsen
2001-10-27 15:00 Alain Knaff
2001-10-27 15:15 ` Alexander Viro
2001-10-27 17:12 ` Alain Knaff
2001-10-27 17:42 ` Alexander Viro
2001-10-27 18:00 ` Alain Knaff
2001-10-27 18:13 ` Alexander Viro
2001-10-27 18:26 ` Alexander Viro
2001-11-06 7:01 ` Richard Gooch
2001-11-06 7:03 ` Alexander Viro
2001-11-06 7:19 ` Richard Gooch
2001-11-06 7:22 ` Alexander Viro
2001-10-27 19:13 ` Alain Knaff
2001-10-27 19:19 ` Alexander Viro
2001-10-27 19:26 ` Alain Knaff
2001-10-28 20:40 ` Alain Knaff
2001-10-28 20:57 ` Peter T. Breuer
2001-10-29 5:38 ` Alain Knaff
2001-10-29 6:07 ` Alexander Viro
2001-10-29 6:34 ` Alain Knaff
2001-10-28 21:42 ` Alexander Viro
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=200110181957.f9IJvHh06884@deathstar.prodigy.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®