From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lukasz Kosewski <lkosewsk@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/3] Add disk hotswap support to libata RESEND #5
Date: Mon, 03 Oct 2005 17:09:31 +0100 [thread overview]
Message-ID: <1128355771.26992.1.camel@localhost.localdomain> (raw)
In-Reply-To: <355e5e5e0510030819od4ef8e5l93708588990081da@mail.gmail.com>
On Llu, 2005-10-03 at 11:19 -0400, Lukasz Kosewski wrote:
> You mean something like "echo scsi-remove-single-device a b c d" >
> /proc/scsi/scsi? I guess the sysfs equivalent?
>
> > - Interface for user to say "have swapped"
>
> I suppose ditto.
Yes. A lot of PATA does swapping only if you tell it first so it can
kill IORDY or tristate the bus.
> > - Post hotswap need to reconfigure both drives as if from scratch
>
> Hmm, this seems far more complicated... basically during a swap
> operation, we have to shut down all I/O to the other drive on the
> cable (if there is one), if I read you correctly, and then reconfigure
> both drives once one is plugged in.
Yes.
> How about this; I want this SATA hotswapping stuff to be tested, so
> I'll commit my patches for 'SATA only' for the time being. I'll stare
> at them for a while and then see what kind of PATA-specific if
> statements and hooks are necessary in the code?
Makes sense to me - the PATA stuff is slowly developing and its getting
closer to submittable as bits of the core code get merged.
next prev parent reply other threads:[~2005-10-03 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 1:01 [PATCH 2/3] Add disk hotswap support to libata RESEND #5 Lukasz Kosewski
[not found] ` <017101c5c39b$95699900$1b00a8c0@FRSNOTI>
2005-09-27 21:47 ` Lukasz Kosewski
2005-09-28 19:10 ` Jeff Garzik
2005-09-28 23:20 ` Alan Cox
2005-10-03 15:19 ` Lukasz Kosewski
2005-10-03 15:53 ` Jeff Garzik
2005-10-03 16:09 ` Alan Cox [this message]
2005-10-03 14:30 ` Lukasz Kosewski
2005-10-03 15:47 ` Jeff Garzik
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=1128355771.26992.1.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkosewsk@gmail.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;
as well as URLs for NNTP newsgroup(s).