linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Wilcox <matthew@wil.cx>, Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] Remove sync waiting code from libata
Date: Sat, 08 Sep 2007 22:33:33 +0200	[thread overview]
Message-ID: <46E3071D.8010202@gmail.com> (raw)
In-Reply-To: <20070908194714.5915dd10@the-village.bc.nu>

Alan Cox wrote:
>> async probing also keeps device numbering stable.  As long as the device
>> responds within ten seconds (and the current code has half a second as
>> the timeout), it'll get the same number it would have had, even though
>> other hosts have successfully completed their probes during that time.
> 
> The usual probe time for a device which is spun down is nearer 30 seconds.

libata probing is done differently tho.  It goes like...

1. libata EH probes all hardware.  Things can take quite long here but
SCSI isn't really involved.

2. After libata EH is finished, SCSI host scan is invoked.  It doesn't
do much.  When SCSI probing command reaches libata-scsi, it just fakes
the replies from the information gathered in #1 - No actual ATA reset or
command is issued.  If there are multiple devices on a host (ATA port),
this rapid probing makes SCSI host scan code fail GFP_ATOMIC allocation
from time to time.  This is why the @sync hack was used.

Thanks.

-- 
tejun

      reply	other threads:[~2007-09-08 20:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07  2:46 [PATCH] Remove sync waiting code from libata Matthew Wilcox
2007-09-08  8:14 ` Tejun Heo
2007-09-08 17:17   ` Matthew Wilcox
2007-09-08 17:36     ` Tejun Heo
2007-09-08 18:47     ` Alan Cox
2007-09-08 20:33       ` Tejun Heo [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=46E3071D.8010202@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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).