linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: boac@wanadoo.nl, linux-ide@vger.kernel.org
Subject: Re: Hotplug drives on vt8251 with ahci module
Date: Thu, 22 Jun 2006 08:16:42 -0400	[thread overview]
Message-ID: <449A8A2A.2070102@rtr.ca> (raw)
In-Reply-To: <449A47EA.90601@gmail.com>

Tejun Heo wrote:
>
> About the disabling on hardreset failure...  Maybe there is some room 
> for improvement - e.g. leave PHY status interrupts alive if it's not 
> causing interrupt storm, but I'm not sure whether the benefits would 
> outweigh the cost.
> 
> Leaving the port frozen (disabled & interrupts plugged) is a safety 
> measure libata implements.  The driver isn't sure in what state the 
> controller and the attached device are in as they are not responding 
> even to the 'hard' reset, so it assumes the worst and shuns the port.
> 
> As I wrote above, you can ask libata to retry by explicitly telling 
> libata to rescan the bus.  I thought that should be enough when I was 

MMm.. sounds like libata should do that periodic polling,
rather than relying on the end-user to do it.  Right?  :)

So the best of both approaches from above:  mask the interrupts
and leave them off, but periodically poll for phy status changes.

??

  reply	other threads:[~2006-06-22 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21  7:42 Hotplug drives on vt8251 with ahci module Aalderd Bouwman
2006-06-21 14:01 ` Tejun Heo
2006-06-22  7:16   ` Aalderd Bouwman
2006-06-22  7:34     ` Tejun Heo
2006-06-22 12:16       ` Mark Lord [this message]
2006-06-23 11:42         ` Tejun Heo
2006-06-22 13:00   ` Aalderd Bouwman
2006-06-23  3:52     ` Tejun Heo
2006-06-23  8:12       ` Tejun Heo
2006-06-24 18:02       ` Aalderd Bouwman

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=449A8A2A.2070102@rtr.ca \
    --to=liml@rtr.ca \
    --cc=boac@wanadoo.nl \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).