From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: alain@linux.lu
Cc: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Poor floppy performance in kernel 2.4.10
Date: Sun, 28 Oct 2001 21:57:59 +0100 (MET) [thread overview]
Message-ID: <200110282057.f9SKvxo15573@oboe.it.uc3m.es> (raw)
In-Reply-To: <200110282040.f9SKe6M02113@hitchhiker.org.lu> from "Alain Knaff" at "Oct 28, 2001 09:40:05 pm"
"A month of sundays ago Alain Knaff wrote:"
> Appended to this mail is the "long live the struct block_device"
> patch. It includes the stuff covered in the last patch as well. The
> issue of stopping transfers in progress is not yet addressed.
Errr .. haven't read the patches. But are you doing something so that
the semantics of the action taken after a media check fails can
be overridden? The current invalidate_inodes is too strong for me,
since I am proxying a remote device, and I don't want to kill
_all_ the local file descriptors when the remote media disappears.
I need to at least continue to send down local ioctls!
No, no suggestions of an extra control device, please. Simplicity.
> +
> static struct block_device_operations floppy_fops = {
> open: floppy_open,
> release: floppy_release,
> ioctl: fd_ioctl,
> check_media_change: check_floppy_change,
> revalidate: floppy_revalidate,
> + can_trust_media_change: floppy_can_trust_media_change
> };
and I'd like to have "invalidate" as a method too.
Peter
next prev parent reply other threads:[~2001-10-28 20:57 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
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-10-27 19:02 ` more devfs fun Alexander Viro
2001-10-27 19:16 ` Alexander Viro
2001-10-27 19:50 ` more devfs fun (Piled Higher and Deeper) Alexander Viro
2001-10-27 20:06 ` Alexander Viro
2001-10-27 21:09 ` Ryan Cumming
2001-10-27 21:22 ` Alexander Viro
2001-10-28 1:00 ` Rik van Riel
2001-10-28 8:45 ` Richard Gooch
2001-10-28 9:54 ` Alexander Viro
2001-10-28 12:27 ` Roman Zippel
2001-10-28 13:16 ` Alexander Viro
2001-10-28 22:31 ` Richard Gooch
2001-10-28 23:11 ` Alexander Viro
2001-10-27 21:01 ` Alexander Viro
2001-11-06 6:35 ` Richard Gooch
2001-11-06 7:10 ` Alexander Viro
2001-11-06 7:14 ` Richard Gooch
2001-11-06 7:17 ` Alexander Viro
2001-11-06 20:14 ` Richard Gooch
2001-10-28 10:06 ` Lorenzo Allegrucci
2001-11-06 5:21 ` Richard Gooch
2001-11-06 5:17 ` more devfs fun Richard Gooch
2001-11-06 5:06 ` Richard Gooch
2001-11-06 7:01 ` Poor floppy performance in kernel 2.4.10 Richard Gooch
2001-11-06 7:03 ` Alexander Viro
2001-12-09 5:38 ` Devfs races with block devices Richard Gooch
2001-11-06 7:19 ` Poor floppy performance in kernel 2.4.10 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-19 16:58 Manfred Spraul
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
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
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=200110282057.f9SKvxo15573@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=alain@linux.lu \
--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®