All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Kosewski <lkosewsk@gmail.com>
To: Ravi Wijayaratne <ravi_wija@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hotswap support for libata
Date: Fri, 2 Sep 2005 23:23:41 -0700	[thread overview]
Message-ID: <355e5e5e05090223231726b94a@mail.gmail.com> (raw)
In-Reply-To: <20050902224418.78897.qmail@web32512.mail.mud.yahoo.com>

On 9/2/05, Ravi Wijayaratne <ravi_wija@yahoo.com> wrote:
> I was wandering whether you could direct me to
> a place where I could find the most up to date
> patches for libata hotplug support you authored.
> 
> Has Jeff Garzik decided to integrate this code
> to 2.6 libata ?

Hey Ravi,

You are on the money in one way; it's September, and I promised
everyone I'd work on it come September.  However, this is a loose
timeline; specifically, I'll be available to work on them come the 6th
of this month.  So expect some more activity then :)

First of all let me clarify something though; these patches are two parts:
- a libata hotswap infrastructure that allows a driver which
understands and properly handles hotplug interrupts to hotswap drives.
- a specific implementation of this infrastructure in the Promise
SATA150 and SATAII150 line of controllers.

I've been getting quite a few emails offline from people excited with
being able to arbitrarily hotswap all Serial ATA drives, and I should
point out that unless people with the other controllers types (ie.
nForce controllers, Sil controllers, etc.) actually add support for
capturing hotswap interrupts and use the hotswap infrastructure, they
will still not support hotplug.  If you send me a controller and the
docs for it, I will add the support and test the b'jesus out of it,
but otherwise only the Promise controllers will have this support.

Here's the current status for all to see:
- I submitted initial patches near the end of July, which were heavily
tested on UP machines and Promise SATA150/SATAII150 Tx4/Tx2 Plus
controllers.  They mostly work.
- Jeff suggested some improvements that would make them work better,
and these improvements work better for a general infrastructure (as
opposed to a sata_promise-centric one).
- I sent in patches implementing the improvements on the 1st of
August.  They weren't tested at all because I didn't have access to
the hardware at that time, but I wanted some feedback.  Those patches
DO NOT WORK, however, they are very close to what I want (I need to
add a workqueue and streamline error-handling a bit more).
- Come the 6th, I'm going to a location where I'll have access to the
controller, as well as UP boxes and an SMP box.  So you can expect new
patches, say, by the 10th or 11th that should be well tested and
robust on UP and SMP machines for Jeff's perusal.

So, if you really want hotswap now now now, you'll have to download my
patches and fiddle with them.  They're available in the kernel mailing
list archives, if you search for 'hotswap libata', they will come up. 
Otherwise, I ask you to be patient for another wek or so and the good
stuff will fall from the sky.

Cheers,

Luke Kosewski

  reply	other threads:[~2005-09-03  6:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02 22:44 Hotswap support for libata Ravi Wijayaratne
2005-09-03  6:23 ` Lukasz Kosewski [this message]
2005-09-03  6:25   ` Lukasz Kosewski
2005-09-03  6:38     ` Jeff Garzik
2005-09-03 17:53       ` Alan Cox

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=355e5e5e05090223231726b94a@mail.gmail.com \
    --to=lkosewsk@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ravi_wija@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.