From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IDE todo list
Date: Sun, 23 Mar 2003 11:49:16 +0100 [thread overview]
Message-ID: <20030323104916.GI837@suse.de> (raw)
In-Reply-To: <1048352492.9219.4.camel@irongate.swansea.linux.org.uk>
On Sat, Mar 22 2003, Alan Cox wrote:
> - Finish verifying 256 sector I/O or larger on LBA48
> [How to handle change dynamically on hotplug ?]
That is basically impossible. How are you going to handle the case where
you have a queue full of 256 request writes, and the plugged in disk
chokes on them? And insolvable unless you start setting aside requests
simply for this purpose. Also breaks the pseudo atomic segments that a
single request represents. This is just way beyond ugly...
This is a generic problem of course, and the typical answer is to go by
the rules of the lowest common denominator if hot plug can cause you
queue limits to be violated (may be other problems than simply max
sector count).
--
Jens Axboe
next prev parent reply other threads:[~2003-03-23 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 17:01 IDE todo list Alan Cox
2003-03-22 17:24 ` Petr Vandrovec
2003-03-22 19:07 ` Alan Cox
2003-03-22 18:03 ` Nicholas Wourms
2003-03-22 20:36 ` Alan Cox
2003-03-22 20:33 ` Nicholas Wourms
2003-03-22 23:32 ` Alan Cox
2003-03-23 3:49 ` Petr Vandrovec
2003-03-23 15:41 ` Alan Cox
2003-03-23 9:27 ` Matthias Andree
2003-03-23 11:19 ` Jens Axboe
2003-03-23 11:20 ` Jens Axboe
2003-03-23 12:33 ` Matthias Andree
2003-03-23 10:49 ` Jens Axboe [this message]
2003-03-23 15:23 ` Alan Cox
2003-03-23 14:13 ` Jens Axboe
2003-03-23 21:07 ` Andre Hedrick
[not found] <20030322160012$0f05@gated-at.bofh.it>
[not found] ` <20030322173016$24a8@gated-at.bofh.it>
[not found] ` <20030322180018$5114@gated-at.bofh.it>
2003-03-23 12:14 ` Allan Duncan
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=20030323104916.GI837@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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