All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: DMADIR+AHCI slows boot a lot
Date: Mon, 12 Jun 2006 13:07:43 +0900	[thread overview]
Message-ID: <448CE88F.8040004@gmail.com> (raw)
In-Reply-To: <448CD8FC.5070508@garzik.org>

Jeff Garzik wrote:
> It looks like we will need to implement an "impatient probe".
> 
> I have an SiI PATA<->SATA bridge that requires DMADIR to enable ATAPI. 
> When ATAPI_ENABLE_DMADIR is -not- enabled, it makes a good test case for 
> the EH :)
> 
> See the attached dmesg output, which illustrates that the boot is slowed 
> by several minutes.  It would be ideal if we could execute EH in the 
> background during probe, and simply stop waiting if it takes too long. 
> bootplug should handle any devices that appear after the bus probe gets 
> "too impatient", and stops waiting.

I've encountered similar problems w/ my broken harddisks.  I am thinking 
of the followings.

* implement parallel probing as SCSI does.

* Make EH parametrized by timeouts.  We currently use single worst-case 
timeout for all tries.  I think we need to use shorter timeouts for 
early tries.  This is also true for normal (non-probing) EHs.  When 
device or controller goes dumb, the current EH is way too generous about 
timeouts.

* A related problem is spinup waiting after hotplug for controllers 
which misses the first D2H FIS.  libata currently waits 8 secs 
unconditionally.  If the drive is ready after that, everything is good. 
  If not, it ends up timing out after 30secs and then retries.  I think 
this can be done much better by trying at 5, 10, 15 and 30 secs from 
hotplug event.

Even if we decide to implement the aboves, I guess both are 2.6.19 
materials.

-- 
tejun

      reply	other threads:[~2006-06-12  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12  3:01 DMADIR+AHCI slows boot a lot Jeff Garzik
2006-06-12  4:07 ` 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=448CE88F.8040004@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --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 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.