linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: lkosewsk@gmail.com
Cc: jim.ramsay@gmail.com, Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Add disk hotswap support to libata RESEND #2
Date: Fri, 16 Sep 2005 12:11:52 -0400	[thread overview]
Message-ID: <432AEEC8.3030800@rtr.ca> (raw)
In-Reply-To: <355e5e5e050914214025feee82@mail.gmail.com>

Lukasz Kosewski wrote:
> On 9/6/05, Jim Ramsay <jim.ramsay@gmail.com> wrote:
> 
>>However, I have seen the occasion where a single IRQ is used to signal
>>both a DMA completion AND a hotplug event.  Of course in this case the
>>hotplug event itself would be ignored completely.
>>
>>So I would recommend getting rid of that check entirely.
> 
> 
> Hey Jim,
> 
> Not that I disbelieve you, but do you have an example of a controller
> where this happens?  I've done a lot of testing and never seen this...

I missed the beginning of this discussion,
but here's a data point:

The QStor SATA/RAID controller hardware fully supports hotplug
(and NCQ, TCQ, Host-Queuing, RAID 0/1/10, PM, etc..).

It uses a single interrupt for all onboard events from the four channels.
An internal "status FIFO" provides a readout for the interrupt handler
of recent happenings, in sequence, mixing together DMA-completions
with hotplug-events (insert, removal) and various fault-conditions.

All of this is supported in the out-of-tree qstor driver,
but only simple single-IO is supported by sata_qstor at present.

Dunno if that info is of any use to you in hotplug considerations.
Once the libata infrastructure for hotplug is in place,
I *may* experiment with adding that functionality to sata_qstor.

Cheers

      reply	other threads:[~2005-09-16 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01 10:02 [PATCH 3/3] Add disk hotswap support to libata RESEND #2 Lukasz Kosewski
2005-08-23 19:41 ` Jim Ramsay
2005-08-23 22:43   ` Jim Ramsay
2005-08-23 22:56     ` George Anzinger
2005-08-24  1:20       ` Stefan Richter
2005-08-24 14:03         ` Lukasz Kosewski
2005-08-24 15:11           ` Jim Ramsay
2005-08-24 16:12             ` Jim Ramsay
     [not found]               ` <4789af9e0508291223435f174@mail.gmail.com>
2005-08-29 19:45                 ` Jim Ramsay
2005-09-06 19:02                 ` Jim Ramsay
2005-09-15  4:40                   ` Lukasz Kosewski
2005-09-16 16:11                     ` Mark Lord [this message]

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=432AEEC8.3030800@rtr.ca \
    --to=liml@rtr.ca \
    --cc=jim.ramsay@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkosewsk@gmail.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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).