From: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Suresh Grandhi <Sureshg@ami.com>,
"'linux-ide@vger.kernel.org'" <linux-ide@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: IDE Hotswap
Date: Wed, 29 Sep 2004 03:54:38 +0200 [thread overview]
Message-ID: <200409290354.38440.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <1096407955.14083.45.camel@localhost.localdomain>
On Tuesday 28 September 2004 23:45, Alan Cox wrote:
> On Maw, 2004-09-28 at 22:38, Bartlomiej Zolnierkiewicz wrote:
> > No and such workaround won't work anyway because
> > re-register operation is nothing else but unregister+register.
>
> If you grab the 2.6.8.1-ac patch you can do IDE controller hotplugging
> and a few other things but not yet drive hotplugging. 2.4 can do drive
> hotplug although you need a small -ac patch if you see wrong disk
> geometry data.
>
> For new controllers (ie SATA ones) use Jeff Garzik's serial ATA layer as
> that is a lot cleaner and the SCSI layer already has a good basic
> understanding of hotplug management.
>
> > Any help/support is appreciated.
>
> Except for the dynamic stuff I consider the problem solved. Its up to
> you when and what you merge and I understand why you want to get stuff
> like sysfs there.
Your patch is a nice start but it don't solve main issues, not to even
mention minor stuff like leaving /proc/ide/<chipset> around.
Merging it now is asking for problems.
> For drive level hotplug its actually a lot easier and I guess that is
> the case most users care about. The changes done for 2.6 clean up stuff
drive level hotplug is actually much harder
and it is _required_ for controller level hotplug, no? :)
> like suspend mean the nasties in 2.4 for sequencing have gone away. No
> refcounting needed since the block and fs layer are doing it all for
It helps but you still get bunch of races. Refcounting is _really_ needed.
> you. TTY layer, revoke(), and some other current critical bonfires first
> before I can help with that however.
Fine.
Bartlomiej
next prev parent reply other threads:[~2004-09-29 2:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8CCBDD5583C50E4196F012E79439B45C069657DB@atl-ms1.megatrends.com>
2004-09-28 21:38 ` Bartlomiej Zolnierkiewicz
2004-09-28 21:45 ` Alan Cox
2004-09-29 1:54 ` Bartlomiej Zolnierkiewicz [this message]
2004-09-29 1:50 ` Alan Cox
2004-09-29 12:08 ` Bartlomiej Zolnierkiewicz
2004-09-29 14:35 ` Alan Cox
2004-09-29 18:20 ` Bartlomiej Zolnierkiewicz
2004-09-29 17:46 ` Alan Cox
2002-05-28 16:02 IDE hotswap Marc SCHAEFER
2002-05-29 9:25 ` Marc SCHAEFER
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=200409290354.38440.bzolnier@elka.pw.edu.pl \
--to=bzolnier@elka.pw.edu.pl \
--cc=Sureshg@ami.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--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®